Hello, On šeštadienis 18 Birželis 2011 23:39:50 Modestas Vainius wrote: > > The upside of this aggressiveness is that sensitive environment variables, > that might already have been set before debian/rules, will be overwritten > and won't affect build of the package. I do understand that doing the same > would break backwards compatibility in debhelper, but maybe that's a good > idea to do for compat(9) or at least provide a dh/dh_auto_* option (e.g. > --force- buildflags) to give maintainers a choice to enable this. However, > I very much prefer the former as in my opinion, most package maintainers > will want (or assume) this behavior. Who would want random shell > environment variables to affect package build? What's more, "clean > environment" is even implied in examples of the Debian Policy ifself [1].
Ahh, when I wrote this compat(9) suggestion, I mostly had dh(1) in mind. Forced buildflags by default would not make much sense in the dh_auto_* context (and may be way more harmful than useful). -- Modestas Vainius <mo...@debian.org>
signature.asc
Description: This is a digitally signed message part.
