[OE-core] gcc 4.6 recipes naming

[Richard Purdie]

Hi Khem,

On Mon, 2011-04-18 at 12:18 -0700, Khem Raj wrote:
> I have gcc 4.6 under progress here. As we know the current release is
> 4.6.0. I have been calling the recipes
> to omit the minor release number so the recipes are called
> <recipes>_4.6.bb based on my experiences
> with gcc releases over the years.
> 
> Since the minor releases are bug fix releases and when next bug fix
> release happens the total diff
> of changes from 4.6.0 to 4.6.1 are also released as a single diff
> which can be applied on top of existing
> 4.6.0 tar file to reach 4.6.1
> 
> This makes the upgrade easier for minor releases. I decided not to
> track the release branch since
> that complicates the gcc download as in classic oe
> 
> So for upgrades we can either just take the diff from 4.6.0 to 4.6.1
> and apply on top of 4.6.0 or
> decide to use the new 4.6.1 tar both would be ok as we decide that later.

I think this is just going to confuse people to be honest. I'm happy to
stick to the 4.6.0 naming, then move to 4.6.1 and so forth over time.
People expect to see the .X number else they just get confused about
which patch revision we're at.

What I'm thinking we will do differently to OE is not to have every
point release available but try and stick to the latest. The exception
would be when there is a problem in the point release version which we
don't have a fix for.

Does that sound reasonable?

Cheers,

Richard