[OE-core] [RFC] Utilizing LAYERVERSION_ to identify breaking changes to a layer

Otavio Salvador otavio at ossystems.com.br
Fri Jun 21 00:33:35 UTC 2013


On Thu, Jun 20, 2013 at 7:56 PM, Flanagan, Elizabeth
<elizabeth.flanagan at intel.com> wrote:
> I know I've run into this issue and I'm going to bet that other folks
> have as well.
>
> When running some sort of continuous integration system (in my case,
> yocto-autobuilder), I need to build to at least two releases back. The
> problem is, sometimes, local.conf and bblayers.conf requirements
> change, for example, a layer needs a BBMASK for the prior release but
> can't have it for the current one or a layer gets split so that I need
> to add two directories to BBLAYERS as opposed to just the one that I
> used a few commits back. I currently have no great way of figuring
> that out and it has causes immense amounts of pain.

I am sorry but I didn't follow what it will help. Can you please
provide an example?

I always thought the right way to handle it is to have a branch...

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750



More information about the Openembedded-core mailing list