Re: Building in chroots hides bugs?
Neil McGovern <firstname.lastname@example.org> writes:
> On Tue, Aug 01, 2006 at 05:37:58PM +0200, Goswin von Brederlow wrote:
>> martin f krafft <email@example.com> writes:
>> > also sprach Marco d'Itri <md@Linux.IT> [2006.08.01.1221 +0100]:
>> >> Building in chroots *hides* bugs.
>> > Uh, what? Please give an example.
>> Missing Build-Conflicts aren't found.
>> Auto* scripts "fail" to run because they aren't installed.
>> Users, Groups, dirs, binaries don't exist that would outisde which can
>> influence configure.
> If a package failts to build from source in a chroot environment, it
> will fail to build on the autobuilders, and should thus be considered RC
That are the simple cases.
But many packages don't want to run auto*, don't Build-Depend on them
and their invocation fails but gets ignored. The package then build
Outside the chroot, where you probably have auto* installed the
invocation suddenly works and you get a different generated file that
might or might not fail.
Is that clearer? He was asking for things that work inside but fail