Hi,
On Sat, 01 May 2010, Loïc Minier wrote:
On Wed, Apr 21, 2010, Raphael Hertzog wrote:
The desired outcome is that all package grab the values directly from
dpkg-buildflags and that we can stop exporting the variables from
dpkg-buildpackage. That way calling debian/rules directly and via
On Sat, May 01, 2010 at 01:31:16PM +0200, Kurt Roeckx wrote:
Yes, calling debian/rules directly or using dpkg-buildpackage
having the same result is clearly the behaviour we want, which is
something we don't have now. dpkg-buildflags should be used by
packages just like dpkg-architecture. So
On Wed, Apr 21, 2010 at 09:10:54AM +0200, Raphael Hertzog wrote:
Package: debian-policy
Severity: wishlist
With dpkg 1.15.7 just uploaded to sid, there's now a dpkg-buildflags
command that should be used to initialize CFLAGS, LDFLAGS, CPPFLAGS,
FFLAGS, CXXFLAGS. It offers some flexibility
Hey
Great to this see effort!
On Wed, Apr 21, 2010, Raphael Hertzog wrote:
The desired outcome is that all package grab the values directly from
dpkg-buildflags and that we can stop exporting the variables from
dpkg-buildpackage. That way calling debian/rules directly and via
Bill Allombert bill.allomb...@math.u-bordeaux1.fr writes:
On Wed, Apr 21, 2010 at 09:10:54AM +0200, Raphael Hertzog wrote:
Package: debian-policy
Severity: wishlist
The desired outcome is that all package grab the values directly from
dpkg-buildflags and that we can stop exporting the
On Wed, 21 Apr 2010, Jonathan Nieder wrote:
On the other hand, many packages already support the noopt option,
usually with code like the following:
ifeq (,$(filter noopt,$(DEB_BUILD_OPTIONS)))
CFLAGS = -g -O2
else
CFLAGS = -g -O0
endif
In particular, they override any value
On Wed, 21 Apr 2010, Bill Allombert wrote:
Suppose user set CFLAGS to XXX. How C files should build ?
Have you read the dpkg-buildflags manual page? If the user wants to modify
CFLAGS he doesn't set it manually but he uses one of the facility to
extend/override it. The result returned by
On Thu, Apr 22, 2010 at 08:46:50AM +0200, Goswin von Brederlow wrote:
Bill Allombert bill.allomb...@math.u-bordeaux1.fr writes:
On Wed, Apr 21, 2010 at 09:10:54AM +0200, Raphael Hertzog wrote:
Package: debian-policy
Severity: wishlist
The desired outcome is that all package grab the
Raphael Hertzog wrote:
On Wed, 21 Apr 2010, Jonathan Nieder wrote:
Given that it will probably be a while before this tool is used
universally, what benefit does an existing package with code like the
above get from switching to using dpkg-buildflags?
It will allow users of source packages
Package: debian-policy
Severity: wishlist
With dpkg 1.15.7 just uploaded to sid, there's now a dpkg-buildflags
command that should be used to initialize CFLAGS, LDFLAGS, CPPFLAGS,
FFLAGS, CXXFLAGS. It offers some flexibility for the local admin and for
the user to override/extend the default
Hi,
Raphael Hertzog wrote:
With dpkg 1.15.7 just uploaded to sid, there's now a dpkg-buildflags
command that should be used to initialize CFLAGS, LDFLAGS, CPPFLAGS,
FFLAGS, CXXFLAGS.
Neat tool; thanks for writing it.
Even without the support of policy, policy already indicates an
obvious
On Wed, Apr 21, 2010 at 09:10:54AM +0200, Raphael Hertzog wrote:
Package: debian-policy
Severity: wishlist
The desired outcome is that all package grab the values directly from
dpkg-buildflags and that we can stop exporting the variables from
dpkg-buildpackage. That way calling debian/rules
12 matches
Mail list logo
