Modestas Vainius wrote: > All examples of "minimal" dh rules have been recommending contrary all this > time.
Also, where I said "policy has required" I should have said just recommended. > Many packages will be broken unless this is dealt with in dh. > Personally, I don't see why this can't be fixed in dh at new compat level > (with an dh option to disable this auto-export of buildflags). 99,9% of > packages will have to use dpkg-buildflags anyway so it is just pointless to > have $(dpkg-buildflags --export=make) in each and every minimal dh rules file. Yes, I agree with you (hence the cc to Bug#560070). Thinking more clearly about it, I wonder if dpkg-buildpackage has to stop exporting those variables soon after all. Maybe there could be an option or envvar to stop exporting them (to help people test their packages) and they could continue to be exported by default to support old packages, just like the dpkg-architecture variables are. The big downside: if the architecture variables are any indication of what to expect, new maintainers would use the exported compiler flags. It's too subtle. In any scenario, I think debhelper is the place to make the first step. :( -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
