I forgot to mention that the other major effect of the new upstream
versioning scheme is that now the convenience symlinks are renamed on
each major gcc release. Previously we have used the gcc-4/gcc++-4
symlinks in %p/bin for each major release. For the gcc5 package, this
will be gcc-5/g++-5 and then gcc-6/gcc++6 when the gcc6 package
arrives. Package maintainers will have to watch out for that one as
you can easily call the wrong gcc version. FYI.
Jack
On Wed, Apr 22, 2015 at 9:00 AM, Jack Howarth <howarth.at.f...@gmail.com> wrote:
> In case anyone is confused, upstream FSF gcc has adopted a new
> version numbering scheme starting with today's gcc 5.1.0 release. The
> significance of the digits is now shifted one decimal point to the
> left. Each major release now increments the major version number
> (5.x.y, 6.x,y, etc). The development releases are versioned as .0.0
> (5.0.0, 6.0.0, etc), the release candidates are .0.1 (5.0.1, 6.0.1,
> etc) and the initial releases are .1.0 (5.1.0, 6.10, etc). The first
> maintenance release of gcc 5 will be 5.2.0. Thus the suffix of the gcc
> 5 compiler name is now simply -fsf-5.
> Jack
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
