[oe] [RFC] turning conf/machine into a set of bblayers

[Maupin, Chase]

> -----Original Message-----
> From: openembedded-devel-bounces at lists.openembedded.org
> [mailto:openembedded-devel-bounces at lists.openembedded.org] On Behalf Of
> Frans Meulenbroeks
> Sent: Thursday, October 21, 2010 7:01 AM
> To: openembedded-devel at lists.openembedded.org
> Subject: Re: [oe] [RFC] turning conf/machine into a set of bblayers
> 
> 2010/10/21 Richard Purdie <rpurdie at rpsys.net>:
> > On Thu, 2010-10-21 at 12:20 +0200, Frans Meulenbroeks wrote:
> >> 2010/10/21 Graeme Gregory <dp at xora.org.uk>:
> >>
> >> >>
> >> > Such a pity git doesnt have increasing rev numbers, a cool adition
> would
> >> > be a flag in layer that showed the last rev of core it was tested
> with.
> >> >
> >> > Layer was tested with core 1 but core is now 999 would give an
> >> > indication on drift between layers and core.
> >> >
> >> > Graeme
> >>
> >> Triggered by this (and apologies if I am drifting off-topic).
> >> It would be nice if with amend.inc you could specify the PR of the
> >> underlying recipe that this amend is for (and get a warning or error
> >> if there is a mismatch)
> >
> > For reference poky now has the PRINC = "x" variable which increases the
> > base PR by x, assuming a standard format PR value. This is intended for
> > use in .bbappend files.
> >
> > Cheers,
> >
> > Richard
> >
> 
> Maybe I was not clear enough on this, but my proposal would be that
> you could say in your amend file something like
> BASEPR_CHECK("r12")
> or something like that (I did not really think about what the best
> syntax would be).
> 
> If you were building and the base recipe did not have the PR you
> specified you'd get a warning (or maybe even an error) so you would
> know that something changed under water.

I haven't tried this myself yet, but if you wanted to tie to a particular PR of the base recipe wouldn't you just put the amend.inc in your overlay at recipes/blah/blah-version-pr directory?

> 
> Best regards, Frans
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel