Martin Jansa martin.jansa at gmail.com
Tue Mar 23 09:47:57 UTC 2010

On Mon, Mar 22, 2010 at 03:26:53PM -0700, Chris Larson wrote:
> Greetings all,
> Thoughts? Questions? Concerns?  I've been wondering if this is really
> worthwhile, but I think it is.  I think there is value in keeping old
> versions around, but this allows us to avoid cluttering up the repository as
> much, and makes it so that one change to a recipe can affect all the
> versions in that range by default, or all versions, rather than just the one
> version you tested.  Of course, ideally you'd test all versions, but that's
> the case today too, its just that now our recipes get bitrotted instead.
>  Personally, I'd rather see the old version content continue to be brought
> forward by default, and if it fails to build with that, we fix it, but it's
> easier to fix a build than to unclutter the repository.
> I'm hoping to get some input on this :)

For me it seems easier to read shared stuff in .inc and then multiple
files with just include on .inc and checksums. Sometimes with additional
patch or some fix only for particular version, instead of one a bit
longer file with OVERRIDES.

But maybe it's just lack of imagination on my side.

Also as I stated in some other thread, I think it's usefull to have one version
of each major version which was in OE (probably latest from each range
you have in nano.bb example), because to test 5 version at least if
patches apply cleanly and it builds ok, is much faster than 42 version
from example.


uin:136542059                jid:Martin.Jansa at gmail.com
Jansa Martin                 sip:jamasip at voip.wengo.fr 

More information about the Openembedded-devel mailing list