On 03/01/2010 11:05 AM, Tom Rini wrote:
On Sun, 2010-02-28 at 21:09 +0100, k.kooia wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 27-02-10 22:27, Tom Rini wrote:
On Sat, 2010-02-27 at 20:46 +0000, Phil Blundell wrote:
On Sat, 2010-02-27 at 16:56 +0000, Graeme Gregory wrote:
NAK on creating extra levels.
Changing the level where recipes are held is not an option do to the way
you tell bitbake how to find them.
BBFILES = "${OE}/org.openembedded.dev/recipes/*/*.bb"
Is that really such a big deal? We seemed to manage to switch BBFILES
from /packages/ to /recipes/ without any major casualties, and I would
have thought that adding an extra level in there would be equally
straightforward. Or of course, even better, the distro-specific recipes
could go in an overlay which the distro config would select.
I think you've just hit on a potentially great idea. Say that
'openembedded' supports 'micro' and 'minimal' as two example
distributions. Move everyone else into their own distro overlay. The
only problem with this, perhaps, is easily adding the distro overlay
itself into the right env vars. :(
Move every distro out of OE, that way people need to set the overlays
correctly.
This does mean that we abandon the "sharing" aspect that started OE
since every little "improvement" will be done in the distro overlay
instead of OE.
Outside of the OE repo, no. Outside of "conf/" yes. And yes, this
would require some re-org, perhaps. Or perhaps not (and we make
something like contrib/ but, I don't know, I suck at naming). And yes,
with an updated local.conf.sample, getting the overlay stuff right is
trivial.
But yes, not generically done at all improvements would end up in the
distro overlay until someone wanted to fix it generically.
Think of it this way, it would also make it easier to show how to make a
"custom Angstrom" the right way, rather than cp
conf/distro/angstrom-2008.1.conf conf/distro/mydistro.conf which I have
gathered would be a good thing.
I am also in the all or nothing camp. If we leave any distro specific
data in the OE repository, people will continue to copy it and start
committing it back. Also, by leaving one or two distros in tree, people
will use them as test cases and catch issues that will impact the out of
tree distros.
Although there may be some short term pain, I believe this will have
long term benefits for the project.
Philip
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
