On 13/05/2016 20:44, Andrew Schulman wrote:
* a few packages mistakenly use DEPENDS
A few packages mistakenly use DEPENDS rather than DEPEND, which is
silently ignored
I'm surprised none of them are mine. It confuses me every time that I have to
use REQUIRES, but DEPEND instead of DEPENDS. I
On 13/05/2016 16:33, Jon Turney wrote:
Recently I've done a little prototyping of a system to build from
uploaded source packages in a VM, to verify that they recreate packages
with the same contents as the uploaded packages.
Issues I noted were:
* a handful of packages are oddities
These of
On May 13 15:33, Jon Turney wrote:
>
> Recently I've done a little prototyping of a system to build from uploaded
> source packages in a VM, to verify that they recreate packages with the same
> contents as the uploaded packages.
>
> Issues I noted were:
> [...]
> * a handful of packages are oddi
Am 13.05.2016 um 16:33 schrieb Jon Turney:
Out of the 3135 cygported packages for x86, only 175 set DEPEND.
I don't know how we can ensure DEPEND contains accurate information
without some sort of build service which tests that it does.
That's the trouble exactly. There is no way to find out
> * a few packages mistakenly use DEPENDS
>
> A few packages mistakenly use DEPENDS rather than DEPEND, which is
> silently ignored
I'm surprised none of them are mine. It confuses me every time that I have to
use REQUIRES, but DEPEND instead of DEPENDS. I have to go look it up again once
or tw
Recently I've done a little prototyping of a system to build from
uploaded source packages in a VM, to verify that they recreate packages
with the same contents as the uploaded packages.
Issues I noted were:
* build time dependencies aren't recorded
Out of the 3135 cygported packages for x8
