[arch-dev-public] Punishment needed for not building in a chroot

Allan McRae allan at archlinux.org
Sun Dec 6 19:18:06 EST 2009

Daenyth Blank wrote:
> On Sun, Dec 6, 2009 at 17:53, Allan McRae <allan at archlinux.org> wrote:
>>  There is _no_ excuse not to use them.
> I don't have enough hard drive space to create a build chroot. That
> being said, I try to use namcap and also try to resolve any bug
> reports within the same day it's assigned. Most of the time I don't
> get any issues.

Seriously? A chroot takes ~600MB.  At build time, even for the most dep 
heavy application, I doubt you will go much beyond 1GB plus space for 
the build files.  Say 1.5GB for most packages.

How do you build packages against [(community-)testing] or not
[testing] as required?  Or do you not help in the rebuilds for library
soname bumps?

I am very much of the opinion that if you can not build a package in a 
clean chroot, then you should not build the package at all.  Fixing a 
bug quickly is no excuse for making the bug in the first place.


More information about the arch-dev-public mailing list