Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.

[Kurt Roeckx <kurt@roeckx.be>]

On Wed, Apr 21, 2010 at 09:10:54AM +0200, Raphael Hertzog wrote:
> Package: debian-policy
> Severity: wishlist
> 
> With dpkg 1.15.7 just uploaded to sid, there's now a dpkg-buildflags
> command that should be used to initialize CFLAGS, LDFLAGS, CPPFLAGS,
> FFLAGS, CXXFLAGS. It offers some flexibility for the local admin and for
> the user to override/extend the default flags used during a package
> compilation.
> 
> dpkg-buildpackage continues to export them to not break packages but it
> exports the value returned by dpkg-buildflags.
> 
> The desired outcome is that all package grab the values directly from
> dpkg-buildflags and that we can stop exporting the variables from
> dpkg-buildpackage. That way calling debian/rules directly and via
> dpkg-buildpackage should give the same result.

Yes, calling debian/rules directly or using dpkg-buildpackage
having the same result is clearly the behaviour we want, which is
something we don't have now.  dpkg-buildflags should be used by
packages just like dpkg-architecture.  So I'm in favour of
recommending it.


Kurt