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

To: Jonathan Nieder <jrnieder@gmail.com>
Cc: debian-policy@lists.debian.org, Matthias Klose <doko@debian.org>, 628552@bugs.debian.org
Subject: Re: tracking packages using (temporary) work-arounds to build
From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
Date: Fri, 27 Jul 2012 16:06:46 +0200
Message-id: <[🔎] 20120727140646.GB26557@yellowpig>
Mail-followup-to: Jonathan Nieder <jrnieder@gmail.com>, debian-policy@lists.debian.org, Matthias Klose <doko@debian.org>, 628552@bugs.debian.org
In-reply-to: <[🔎] 20120726223258.GA2978@burratino>
References: <4DE33307.1060505@debian.org> <[🔎] 20120720211543.GB5841@burratino> <[🔎] 20120726204343.GH2230@yellowpig> <[🔎] 20120726223258.GA2978@burratino>

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 can use them in the patch, but it would be much better not to apply the patch at all.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.

Reply to:

References:
- Re: tracking packages using (temporary) work-arounds to build
  - From: Jonathan Nieder <jrnieder@gmail.com>
- Re: tracking packages using (temporary) work-arounds to build
  - From: Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
- Re: tracking packages using (temporary) work-arounds to build
  - From: Jonathan Nieder <jrnieder@gmail.com>

Prev by Date: Re: tracking packages using (temporary) work-arounds to build
Next by Date: Re: tracking packages using (temporary) work-arounds to build
Previous by thread: Re: tracking packages using (temporary) work-arounds to build
Next by thread: Re: tracking packages using (temporary) work-arounds to build
Index(es):
- Date
- Thread