So effectlvely the old usage of the major version has been discarded with the previous usage of the minor version mapped to it. Likewise for the previous usage of the patch version now mapped to the minor version. I am just trying to clarify this as I have to adjust my packaging of FSF gcc in the fink project. For example, previously we used -program-suffix=-fsf-4.9 but now this will have to be -program-suffix=-fsf-5. Likewise we buried the release with --prefix=%p/lib/gcc4.9 but now this will have to be --prefix=%p/lib/gcc5 for the gcc 5 release series.
On Sun, Mar 22, 2015 at 1:57 PM, Jonathan Wakely <jwakely....@gmail.com> wrote: > On 22 March 2015 at 17:28, Jack Howarth wrote: >> Is this the policy going forward for the 6.0 release as well? > > Yes, as it says on that webpage. > >> If it is >> being done just to avoid the stigma of a .0 release, it really smacks >> of being too cute by half. > > That's not the reason, there's a rationale on the webpage too. > > If someone says they have 4.9.0 it could be the final release or a > trunk build from 9 months earlier, which would be a very different > compiler. Similarly, 4.9.1 would be the final release or a build on > the branch from the day after 4.9.0 was released. > > With the new scheme the __GNUC_PATCHLEVEL__ component is different for > final releases and snapshots.
