In 2010 CDBS grep support for DEB_BUILD_OPTIONS=debug (see https://bugs.debian.org/599218 ), but I now realize that the option is not documented in Policy.
I wonder, if I should drop that from CDBS, or if not if we should put it in Policy? I am aware that debug symbols (e.g. CFLAGS=-g) is set by default, and stripped after build for normal packages except when DEB_BUILD_OPTIONS=noopt is set. Setting DEB_BUILD_OPTIONS=debug does "./configure --enable-debug" in CDBS, which e.g. for libucommon not only sets -g but also -DDEBUG, which seems to affect runtime behavior in ways unsuitable for production use. Searching briefly with codesearch.debian.net reveals a bunch of non-CDBS packages supporting DEB_BUILD_OPTIONS=debug, but apparently simply to enable -g and also the ones I looked at didi it the old sloppy way using $(findstring ...) instead of $(filter ...) so perhaps they are all old packages not reflecting current best practices. Opinions? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
