Hi, On Wed, 12 May 2010, Joey Hess wrote: > I'm not sure how all this ties in with the new dpkg-buildflags command. > The right thing might be for debhelper to use dpkg-buildflags to get > default (and configurable) values. > > * Introduce a new script called dpkg-buildflags: its purpose is to retrieve > compilation flags and it should be used within debian/rules to pass > the right compilation flags to the build process. dpkg-builpackage still > exports them to not break packages currently relying on them but packages > should now start using dpkg-buildflags instead. Closes: #560070
I was about to file a bug so that debhelper start using dpkg-buildflags and I came across this bug. I agree with Steve that debhelper should really set up the environment in dh_auto_configure and dh_build. I'm not sure what's the best way to do that integration however (not being an autoconf expert). At the very least, I suggest that you export the variables that dpkg-buildpackage is exporting if they are not already set. That way, the day when dpkg-buildpackage stops setting them all packages using tiny rules files would not break. (You can even use Dpkg::BuildFlags directly instead of dpkg-buildflags if you want to avoid some perl forks) But maybe there's a cleaner interface to enforce build flags that involves only changes at the ./configure stage? I guess the analysis needs to be done for each of the build system that dh currently supports. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
