[OE-core] gcc 4.6 recipes naming

Richard Purdie richard.purdie at linuxfoundation.org
Tue Apr 19 22:37:33 UTC 2011


On Tue, 2011-04-19 at 10:33 -0700, Khem Raj wrote:
> On Tue, Apr 19, 2011 at 8:01 AM, Richard Purdie
> > 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.
> 
> usually later minor release will always be better (since they are bugfixes only)
> so chances are less that we will regress

Agreed, I'm just being clear what the expectations are! :)

> > Does that sound reasonable?
> >
> 
> Yes having just one minor release at a time makes it easier certainly.
> I was trying to make it easy to push updates and we could avoid some
> git operations and logs would be straighter too since recipes would live
> longer otherwise we will be git mv'ing them every 6 months when release happens.

I think this is fine, we do this for the other recipes too.

Cheers,

Richard








More information about the Openembedded-core mailing list