Re: Let's remove mips, mipsel, s390, ...
Kevin Mark <kmark+debian-devel@pipeline.com> writes:
> would it make sense to examine the queue to see if any packages have
> similar build dependencies and then move them to the top of the queue so
> they build immediately after the current one?
> or to re-sequence the queue to group package with similar build
> dependencies.
> -Kev
That only works if you would just install/purge the difference between
Build-Depends of the last and next build. The official buildds don't
do that.
My local, experimental buildd includes this in the API but for lack of
time the current "update-build-depends <dist> <old-package=version>
<new-package=version>" script just does purge all old, install all new
(and on amd64 I rarely care).
I also have a ToDo item to give out packages to buildds in groups with
overlapping Build-Depends so as to take advantage of the above. So a
buildd asking for things to build would get item 1, 3 and 7, all being
kde packages, instead of 1, 2 and 3. But that's just an idea for now.
MfG
Goswin
Reply to:
- References:
- Re: Let's remove mips, mipsel, s390, ...
- From: Bernd Eckenfels <ecki@lina.inka.de>
- Re: Let's remove mips, mipsel, s390, ...
- From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
- Re: Let's remove mips, mipsel, s390, ...
- From: Wouter Verhelst <wouter@debian.org>
- Re: Let's remove mips, mipsel, s390, ...
- From: Kevin Mark <kmark+debian-devel@pipeline.com>