Re: [PATCH 0/5] Enable VPN support in ConnMan

[Tomas Frydrych <tf+lists.yocto@r-finger.com>]

On 13/05/13 15:53, Phil Blundell wrote:
> On Mon, 2013-05-13 at 12:32 +0100, Tomas Frydrych wrote:
>> On 13/05/13 12:06, Burton, Ross wrote:
>>> The problem with bbappends is that they break every time the package
>>> in oe-core changes version.
>>
>> I see this as a good thing; if I maintain a bbappend, I want to know
>> when the base package changes its a version, and I get an immediate
>> error due to bbappend to a non-existent file.
> 
> Personally, for the .bbappends that I maintain, I would much rather not
> have to go around renaming a bunch of files every time I merge a new
> version of oe-core and all the recipes get upgraded. 
> 
> But, if you enjoy the errors, you could easily enough get them back even
> if the filenames didn't change:
> 
> python() {
>     tolerable_pvs = [ '1.0', '1.1', '1.2' ]
>     pv = d.getVar('PV', True)
>     if not pv in tolerable_pvs:
>         bb.fatal("encountered intolerable version %s of underlying recipe, please adjust me accordingly" % pv)
> }
> 
> or something.  One could wrap that in some extra sugar and put it in
> base.bbclass if having the boilerplate in each .bbappend is unappealing.

I do like this approach; I'd probably wrap it in a class and let the
bbappend maintainer to decide if their bbappend deserves this or not.


Tomas