Re: NMU and ./configure
> > Anybody should be able to build a package when its build-time dependencies
> > are satisfied and end up with the same result as anyone else. This is
> > a policy recommendation.
> But, if the user has something *extra* installed, that the configure script
> picks up and uses, because it is optional for the package build... you do
> the math.
> For this situation, I would suggest that we start to be really strict, and
> use chroot jails for *all* builds.
Hm. In the original example, gimp1.1's configure script searches for
"lpc" and "lpstat" binaries before enabling printer support in the
print plug-in. So:
1. If you have the lpr package installed, you get "lpc" support in
2. If you have the lprng package installed, you get both "lpc" and
"lpstat" support in the plug-in.
3. If you have no lpc or lpstat binary on your system when you bild
gimp1.1, you won't be able to print to any printers, even if you
install lpr or lprng later on.
I support the chroot jail concept, but in this case gimp1.1 would
need to build-depend on lpr to get a proper build.