>>"Randolph" == Randolph Chung <[EMAIL PROTECTED]> writes:
Randolph> sure eventually all packages will move to the new scheme,
Randolph> and everything will be happy. i'm not suggesting anything
Randolph> more or less.
Then it can't be made mandatory from the word go, if every
single
> 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
Randolph Chung <[EMAIL PROTECTED]> cum veritate scripsit:
> one problem is that some packages have build-dependency chains that
> when resolved completely are very deep, and sometimes contains dependency
> cycles. One could argue that these are bugs, but they seem difficult to fix
> in some cases
>>"Randolph" == Randolph Chung <[EMAIL PROTECTED]> writes:
Randolph> Proposal: This is a proposal to add information about a
Randolph> package's build environment to the "changes" file that
Randolph> accompanies the upload of each package. The build
Randolph> environment information contains
On Fri, Mar 15, 2002 at 07:14:44AM -0800, Randolph Chung wrote:
> > > 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, w
> > 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
On Thu, Mar 14, 2002 at 11:08:42PM -0800, Randolph Chung wrote:
> 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
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
8 matches
Mail list logo
