Re: tracking packages using (temporary) work-arounds to build

2012-07-27 Thread Jonathan Nieder
Bill Allombert wrote: >> In 2011, Matthias Klose wrote: >>> Some packages use work-arounds to prevent build failures, because >>> these expose bugs in the build tools; these work-arounds are usually >>> not reverted, and not tracked, or badly tracked (changelogs >>> commenting on "new version of g

Re: tracking packages using (temporary) work-arounds to build

2012-07-27 Thread Bill Allombert
On Thu, Jul 26, 2012 at 05:32:58PM -0500, Jonathan Nieder wrote: > Bill Allombert wrote: > > > What developers would really need is an easy way to apply patches > > selectively on the > > version of gcc used. > > Don't the __GNUC__ and __GNUC_MINOR__ preprocessor symbols work for > that? You ca

Re: tracking packages using (temporary) work-arounds to build

2012-07-26 Thread Jonathan Nieder
Bill Allombert wrote: > What developers would really need is an easy way to apply patches selectively > on the > version of gcc used. Don't the __GNUC__ and __GNUC_MINOR__ preprocessor symbols work for that? Curious, Jonathan -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org

Re: tracking packages using (temporary) work-arounds to build

2012-07-26 Thread Bill Allombert
On Fri, Jul 20, 2012 at 04:15:43PM -0500, Jonathan Nieder wrote: > Hi, > > In 2011, Matthias Klose wrote: > > > Some packages use work-arounds to prevent build failures, because > > these expose bugs in the build tools; these work-arounds are usually > > not reverted, and not tracked, or badly tr

Re: tracking packages using (temporary) work-arounds to build

2012-07-20 Thread Jonathan Nieder
Hi, In 2011, Matthias Klose wrote: > Some packages use work-arounds to prevent build failures, because > these expose bugs in the build tools; these work-arounds are usually > not reverted, and not tracked, or badly tracked (changelogs > commenting on "new version of gcc"). > > These work-arounds