Re: How should OE be used?

[Richard Purdie <rpurdie@rpsys.net>]

On Tue, 2007-09-25 at 04:48 +1000, Lorn Potter wrote:
> I have always thought that oe needed an easier way to choose packages, 
> like buildroot.
> 
> Some gui that can edit all the conf's and task's, and image.bb's 
> painlessly and easily would make a tom of difference.
> The learning curve for oe is too high.

This is something I plan to raise at OEDEM.

It should be relatively well known by now that I want to improve bitbake
to the extent where writing some kind of UI around it is straightforward
and we can start improving the user experience from this angle.

Bitbake trunk now has some foundations for this in place although there
are some gaps and a few regressions that need fixing. There is no new UI
itself yet.

The job isn't actually that difficult, the problem is that the learning
curve anyone implementing it faces with no previous experience is
steep. 

Personally, the big problem I have is the lack of time to do it and I
suspect others with the experience also have time issues :-(.

> Take buildroot, for example. A person can download it, run make 
> menuconfig, set up the system, arch, and select packages, all in one
> go. 
> You do not need to know that you should have to either edit or create 
> your own tasks, or image .bb's, much less the syntax for those files.

Playing devil's advocate, take Poky, for example. A person can
download/check it out, edit one simple configuration file
(comment/uncomment lines), source a file and go :).

So it is possible.

Cheers,

Richard