Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.

2010-04-21 Thread Raphael Hertzog
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 flags

Bug#578421: virtual-packages: Retire java-compiler, java2-compiler and java-virtual-machine

2010-04-21 Thread Niels Thykier
Rene Engelhard wrote: > On Mon, Apr 19, 2010 at 08:33:12PM +0200, Niels Thykier wrote: >> [java{,2}-compiler] >> - default-jdk. If used in an alternative in Build-Depends{,-Indep} then >> pick >> one of the options (The Java Team recommends default-jdk). > > And what are you going to do as

Bug#578664: developers-reference: outdated examples in pkgs/resources.dbk

2010-04-21 Thread David Prévot
Package: developers-reference Version: 3.4.3 Severity: minor Tags: patch Hi, While updating the French translation of the Developer's Reference (currently reviewed on debian-l10n-fre...@l.d.o), I noticed a few outdated mentions. Please find attached a patch on the svn version. Cheers David --

Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.

2010-04-21 Thread Jonathan Nieder
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

Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.

2010-04-21 Thread Bill Allombert
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/

Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.

2010-04-21 Thread Goswin von Brederlow
Bill Allombert 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 variables from >> dpkg-build

Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.

2010-04-21 Thread Raphael Hertzog
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 an

Bug#578597: Recommend usage of dpkg-buildflags to initialize CFLAGS and al.

2010-04-21 Thread Raphael Hertzog
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 dpkg-b