On 09/24/2011 05:48 PM, Ian Jackson wrote:
> Joey Hess writes ("Re: Bits from dpkg developers - dpkg 1.16.1"):
>> Raphael Hertzog wrote:
>>> * dpkg-buildpackage no longer exports
>>> CFLAGS/CXXFLAGS/LDFLAGS/CPPFLAGS/FFLAGS
>>
>> | You don't know how many packages are broken or no longer
>> | policy compliant because they were relying on those environment
>> | variables
>>
>> Who said that? Oh, yeah it was you.
>>
>> How are we supposed to deal with packages that have been broken or made
>> policy incompliant by this change to dpkg?
>
> I'm one of the submitters of one of the bugs which requested this
> change. This is a reversion of dpkg to a previous behaviour, and it
> /un/breaks packages. Or at least I think it unbreaks much more than
> it breaks.
ACtually I think that is true - the exported *FLAGS broke various of the
packages I maintain, mainly due to LDFLAGS breaking the build of Python
extensions or other kinds of plugins.
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprints: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e81ca91.1050...@debian.org
