What if, there was a benefit in building from source, a system that is commonly used by pre-fabricated binary packages, like Arch or any of its forks and desktop flavors? What Arch considers a “clean-chroot” is primarily of need to developers ensuring their package can be both satisfied for all dependencies AND are reproducible, as long as this can be achieved within a constantly rolling distribution. That is open and nearly free condition for you.
Building in a clean chroot prevents missing dependencies in packages, whether due to unwanted linking or packages missing in the depends array in the PKGBUILD. It also allows users to build a package for the stable repositories (core, extra, community) while having packages from [testing] installed.
Scratch most of this for several reasons. We are not developers, we are building our own system like Gentoo-ers, k1ss-ers, Crux-ers, and others do. We want to make sure that each of our packages fits well within the parameters of our specific machine, and it wasn’t built on another machine that may not be 100% compatible to ours. Continue reading