[oe] How should OE be used?

Cliff Brake cliff.brake at gmail.com
Mon Sep 24 16:14:47 UTC 2007


On 9/22/07, Philip Balister <philip at balister.org> wrote:
> For now, I'd like to focus on working out how people use OE and what
> issues they have. Once we understand what problems exist, if any, we can
> discuss solutions.

I use OE in much the same way as Leon.  I find a OE/Bitbake snapshot
that is stable and lock it down for project work.   I generally don't
upgrade until I need a new feature, or I have some time to work
through issues.  I have several dev boards that I use to track the
HEAD that I use for contributing to OE, and keeping up with what is
going on.

For me, this works fine, but then I keep up with what is going on, so
I have a pretty good feel for when it is a good time to upgrade
projects, etc.  The occasional OE user would probably have a much more
difficult time.  I'm not sure a stable branch would help a lot, as it
would consume a lot of developer time that is probably better spent
moving things forward  Perhaps something more like kernel release
process would work where we shoot for stable releases (perhaps
quarterly) where the focus right before the release is to get things
stable for a number of architectures.  But, then I'm not sure there is
a big advantage of this over just doing more/better autobuilds and
testing.

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com




More information about the Openembedded-devel mailing list