On Wed, Feb 10, 2016 at 06:14:30PM +0100, Stephan Sürken wrote: > On Mo, 2015-08-31 at 21:09 +0200, Marc Haber wrote: > > Source: mini-buildd > > Severity: wishlist > > > > Hi, > > > > I have just noticed that a build chroot does not have aptitude > > installed. If the aptitude resolver is used, this results in aptitude > > being installed over and over for every build process. > > > > Is this intentional? If not, aptitude should be part of a build chroot > > that is intended to be used with the aptitude resolver. > > that actually is sort of "intentional"; more precisely, all chroots are > generic, and may potentially be used by any mini-buildd repository -- > only the build requests determine what resolver to be used. > > Maybe just having aptitude pre-installed generally actually brings more > benefits than harm -- in that case, however, I would like to see > 'debootstrap --varinat=buildd' bringing this in.
You're right. > What mini-buildd *could* do is some instance-global > "chroot_extra_packages" option, so the administrator may override > debootstrap if he wants to. > > Keep this open for that? Sounds good. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
