On Fri, 2018-04-06 at 14:58 -0400, Denys Dmytriyenko wrote:
> I understand the need to reduce the support burden. But there are
> some valid 
> cases when you want to use components/layers from a different set of
> releases. 
> 
> It can sometimes be an older component in otherwise newer setup (i.e.
> one 
> layer hasn't been updated yet from rocko, but it still works fine
> with 
> everything else from sumo).
> 
> Alternatively, sometimes you need to bring a newer version of the
> component to 
> your older release - as long as it works for me, I don't want this to
> be 
> artificially restricted.
> 
> In other words, the intention is good, but it needs to be either more
> flexible or allow overriding this from distro config or local.conf...

Whilst I will admit I've not extensively tested it, I think that should
be possible to override things as this only gets validated after all
the layer.conf files are pulled in. It would need to be from the
distro's layer.conf though, or a layer.conf in the build directory as
local.conf comes in much later. Basically its possible but not easy,
which I think is probably the right thing to do here.

Cheers,

Richard
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to