On 05/29/2011 09:10 PM, Raphael Hertzog wrote:
Hi, On Sun, 29 May 2011, Jonathan Nieder wrote:Matthias Klose wrote:There is more than a handful of packages which do not care about dpkg-buildflags yet in debian/rules. Currently it's difficult to tell if a package build honors dpkg-buildflags or not. The only way to do this currently is to edit the config files for a test rebuild.Do you often need to verify if a package supports dpkg-buildflags? In what context?
Jonathan did give some examples. hardening, or a different optimization level by default.
The idea is to add some flags which do not have any effect on the package build, and then look at the build log if these flags are passed to the build. Such flags could be for - CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS: -D__BUILDD_<random-string>__ - LDFLAGS: -z buildd-<random-string> (gold would need a patch for this)Neat idea. Would it be possible to set this up as configuration on buildds so people don't get the strange idea that this is a standard dpkg feature they can rely on? (Cc-ing the buildd-tools developers as a random guess for who could set this up.)Yeah, cc-ing debian-wb-team@lists.debian.org which might be more relevant. I also agree that it could be a good idea but I'm not convinced that dpkg is the right place to impose those fake flags by default.
please make it easy for a developer to test with these flags. If possible, I would like to turn this on when using dpkg-buildpackage.