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

Johannes Löthberg johannes at kyriasis.com
Thu Jun 25 16:58:11 UTC 2015

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
>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.

  Johannes Löthberg
  PGP Key ID: 0x50FB9B273A9D0BB5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1495 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20150625/dad23ff7/attachment.asc>

More information about the arch-dev-public mailing list