On Tue, Sep 08, 2009 at 03:46:55PM -0400, Joey Hess wrote:
I feel that if dh_auto_configure/build is going to provide a default CFLAGS
setting, this will need to wait for the v9 compatability level.
Otherwise there is the risk of breakage.
OK.
I am still, though, not convinced this is within
Steve Langasek wrote:
My understanding is that the dpkg maintainers have already decided in favor
of A.
The only one I can see being problematic is the build flags one, there
might be packages that have started assuming dpkg-buildpackage will
set the flags, so they might fail or
On Thu, Sep 03, 2009 at 02:03:30PM -0400, Joey Hess wrote:
Debian needs to decide either:
A. The variable settings added to dpkg-buildpackage were a bad idea,
both because they may override settings that individual package
build systems more carefully tune, and because they make it
Package: debhelper
Version: 7.3.15
Severity: important
Nothing in a standard dh build (neither dh_auto_configure nor dh_auto_build)
appears to ensure that the standard CFLAGS, -g -O2, are passed to the
upstream build system by default. This means that packages built with
./debian/rules foo
Steve Langasek wrote:
Nothing in a standard dh build (neither dh_auto_configure nor dh_auto_build)
appears to ensure that the standard CFLAGS, -g -O2, are passed to the
upstream build system by default. This means that packages built with
./debian/rules foo (instead of via dpkg-buildpackage)
5 matches
Mail list logo
