Re: automatic recipe upgrades - making them better and sweeter

[Alexander Kanavin <alexander.kanavin@linux.intel.com>]

On 11/07/2017 10:17 PM, Paul Eggleton wrote:

> So there is a method to this madness, but it's less about your use case than
> it is people making customisations that they are best advised to put somewhere
> else - I'm trying to make the user think about where the changes should go
> beforehand, because the nature of devtool finish is that you can't easily go
> back and shift the changes elsewhere after you've run it. It would be trivial
> to add an option that put the recipe back where it came from without you
> having to be explicit though, so we could add that; potentially we could have
> a configuration option to make that the default for you and others who more
> commonly update the base metadata. Otherwise, I'm open to alternative
> suggestions, but preferably I still want to avoid making it easy for users to
> make a mistake and update the original metadata when they really should have
> pointed it at their own layer.

That's fine with me. Unlike specifying version/revision on the command 
line (which at the moment need to be manually determined, and change 
every time), the layer destination is more or less static and can be 
hardcoded in a wrapper (or finger memory).

Alex