[arch-dev-public] Building in a clean chroot

jan at jgc.homeip.net jan at jgc.homeip.net
Fri Jun 26 07:21:12 UTC 2015

> -----Oorspronkelijk bericht-----
> Van: arch-dev-public [mailto:arch-dev-public-bounces at archlinux.org]
> Namens Johannes Löthberg
> Verzonden: donderdag 25 juni 2015 18:58
> Aan: Doug Newgard
> CC: Public mailing list for Arch Linux development
> Onderwerp: Re: [arch-dev-public] Building in a clean chroot
> On 25/06, Doug Newgard wrote:
> >I had two somewhat related bug reports recently. One of made it obvious
> that the
> >packager wasn't building in a chroot. The second one was for a missing
> >makedepends on a package that was added to the repo less than a day
> earlier. I
> >figured this one might be from a dirty chroot, but after contacting the
> >maintainer, it turns out he doesn't build in a chroot for "any" architecture
> >packages.
> >
> >So here we have two people packaging for the repos building outside of
> chroots.
> >Where there's two, there's probably more that just haven't been
> discovered yet.
> >I inquired about this on IRC and was told there is no written policy, they just
> >thought it was understood by all. Is this then something that's currently left
> >to the maintainer's discretion? Is it policy and just not written? Is it
> >something that should be written policy?
> >
> It's considered "highly recommended" but there's no firm policy for it,
> though I agree that there likely should be.

IMHO we should require building in chroots. We have infrastructure for this.

Requiring chroots would be a step closer to https://bugs.archlinux.org/task/43407

More information about the arch-dev-public mailing list