Package: debian-policy
Version: 3.5.6.1
Severity: serious
The debian-policy package is missing a build-dependency on
docbook-utils; the package does not build from source.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> And the bit
> about standards version is a red herring, really: packages are
> supposed to be current with policy (which is why policy froze) -- it
> is just that stable releases have packages that conform to policy as
> it existed then. Packages in Sid need to be current (can't claim
> anci
> > 2. Ideally one might want to recursively list all the dependents of build-
> > dependencies too, but that is probably too expensive to compute.
> On my Pentium 166MHz, the following command took about 10s (real) to
> run, with devscripts (>= 2.6.90) installed:
Thanks, that was good to know.
o
Package: debian-policy
Severity: wishlist
Proposal:
This is a proposal to add information about a package's build environment
to the "changes" file that accompanies the upload of each package. The
build environment information contains the versions of packages used to
build the given package. The
Some time ago, I think there was a proposal to change the way task
packages are put together. Instead of task-* packages, relevant packages
would have something like:
Task: programming/c
If people want the kind of flexibility described in the thread (trees,
subtrees, etc). We should look into imp
I second Branden's proposals.
randolph
--
@..@ http://www.TauSq.org/
()
( >__< )
^^ ~~ ^^
pgpdT4cryfGcZ.pgp
Description: PGP signature
6 matches
Mail list logo
