Re: oe-core cleanup...

[Joshua Lock <josh@linux.intel.com>]

On Thu, 2011-03-03 at 07:21 -0700, Chris Larson wrote:
On Thu, Mar 3, 2011 at 7:14 AM, Chris Larson <clarson@kergoth.com>
wrote:
> > On Thu, Mar 3, 2011 at 7:05 AM, Joshua Lock <josh@linux.intel.com>
wrote:
> >> I agree, in fact yesterday I discovered we have the beginnings of
such a
> >> tool (bitbake-layers) written by Chris. Currently it prints out
which
> >> recipes are being modified by a .bbappend and .bbappend files for
which
> >> no recipe exists.
> 
> Note that it also warns about bbappending to a non-preferred version
> of a recipe, but not bbappending to the preferred version of the
> recipe, to cover the case where a bump of an earlier layer adds a new
> version without removing the old.  I was trying to catch all the cases
> where your local changes might seem "lost" when updating things.

Ah, that's a nice feature that I'd missed (I don't have any such recipes
in the layers I'm using).

> On another note, I was really surprised at just how painless it was to
> create a new standalone tool to do this, considering it bypasses much
> of the infrastructure which the main bitbake tool uses.  There are
> definitely still some hiccups in bitbake we should fix to make it
> easier, but it wasn't bad at all, which was great to see, and we'll
> have to think about what other standalone tools might be useful in the
> long term.
>
Yes indeed. I was pleased when I discovered bitbake-layers and even more
pleased when I saw how concise a program it is.

I'd love to see a wiki-page or some such where we can collaborate on
tools ideas. I'm slowly understanding more and more of BitBake and
gaining an increased appreciation of Python so little hack project ideas
would be welcome.

Cheers,
Joshua
-- 
Joshua Lock
        Yocto Build System Monkey
        Intel Open Source Technology Centre