On Mon, Apr 26, 2004 at 06:08:34PM +0200, Wouter Verhelst wrote: > Maintaining a buildd machine involves keeping a chroot environment > relatively clean.
Yup. Probably the best way of doing this is to debootstrap a new chroot every day. One of the other tricks is that in some cases you probably need to install -dev packages from experimental, but in other cases you'd rather install the -dev packages from unstable. Experimental is kind-of "different" to unstable as far as buildding goes. > [...]; as such, > the burden on the buildd maintainer will be a lot higher than it is on > an unstable buildd maintainer. Yeah; reducing this by offloading it to the package maintainer is a particularly good idea for experimental buildds (eg, mailing the build logs to the maintainer rather than the buildd operator; and having the maintainer sign the .changes files of successful builds). Cheers, aj -- Anthony Towns <[EMAIL PROTECTED]> <http://azure.humbug.org.au/~aj/> Don't assume I speak for anyone but myself. GPG signed mail preferred. Protect Open Source in Australia from over-reaching changes to IP law http://www.petitiononline.com/auftaip/ & http://www.linux.org.au/fta/
signature.asc
Description: Digital signature
