Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and OpenEmbedded
Date: Tue, 25 Aug 2009 12:44:44 +0200	[thread overview]
Message-ID: <4A93C09C.4020901@eclis.ch> (raw)
In-Reply-To: <5f2b60908250214p357b20d5q1de520d50ec2c1fb@mail.gmail.com>

Bj?rn Forsman a ?crit :
> Funny, nobody has commented the "OE+BR merge" I mentioned. Am I the only one
> dreaming of a BR with its easy configuration combined with the package
> set provided
> by OE? But I guess the OE bitbake tool and *.bb files makes a merge
> impossible...

A possible way: Make the BR configuration tool generate the 
corresponding OE configuration for the BR supported subsets.

A better way: Create a sweet OE configuration tool, capable to make BR 
obsolete in term of user experience and system performance (size, speed, 
etc...)

In the long term, even OE will face concurrence from even better concept 
more closely related to the main current distributions. Such candidates 
could be EmDebian or the future Debian Multiarch. ScratchBox have gain 
more and more attention too.

Too many tools fragment the community. I also think that merging the 
bests features from projects with very similar goal will be a benefit 
for everyone in the long term.

Jean-Christian de Rivaz

      reply	other threads:[~2009-08-25 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 13:04 [Buildroot] Buildroot and OpenEmbedded Bjørn Forsman
2009-08-13 13:28 ` Will Newton
2009-08-13 19:55   ` Bjørn Forsman
2009-08-19 20:49     ` Ulf Samuelsson
2009-08-21 18:10       ` Julien Boibessot
2009-08-24 20:59 ` Peter Korsgaard
2009-08-25  9:14   ` Bjørn Forsman
2009-08-25 10:44     ` Jean-Christian de Rivaz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A93C09C.4020901@eclis.ch \
    --to=jc@eclis.ch \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox