From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Revert "kmod: Use base_libdir for installing libkmod"
Date: Thu, 17 May 2012 23:22:51 +0100 [thread overview]
Message-ID: <1337293371.3181.190.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAP9ODKqc5eubLWKrbPowvunHaUX0Fhbk-XLFgH=b+pr8m+tGcQ@mail.gmail.com>
On Thu, 2012-05-17 at 18:51 -0300, Otavio Salvador wrote:
> It is important to state that if OE-Core breaks Meta-OE this is
> crticial. It is not Yocto that people use and many active contributors
> use Meta-OE so it is important and critical to that people. Seems more
> health to the project to give the deserved value to Meta-OE instead of
> badmouth it...
No doubt meta-oe's welfare is indeed critical to those who use it, but
there is a substantial population of oe-core users who don't.
Without wishing to badmouth meta-oe too much, I do get the impression
that its relationship with oe-core is based more on taking than on
giving, and also that meta-oe seems a bit unclear about what exactly its
own mission is. On the one hand it seems to try to be a sort of
unofficial mod for oe-core which adds newer/older/different versions of
some recipes and adjusts features in others. On the other hand it seems
to be a repository for recipes which are of general interest but not
quite "core" enough to be in oe-core. And on the third hand, there
seems to be a view (as Tom alluded to in this thread) that meta-oe
should serve as some sort of staging area for changes which are
ultimately intended for oe-core but perhaps not quite stable enough yet.
As Paul mentioned, the combination of these three things is somewhat
toxic.
Personally I would like to see the meta-oe folks make a bit more of an
effort to contribute worthwhile improvements back to oe-core (and/or put
them in other layers, as seems to be happening with the systemd bits)
rather than just keeping them as part of the meta-oe monolith
indefinitely. And, in parallel with that, I think it would make sense
to split meta-oe into three or maybe more separate layers: one which is
purely a collection of "extra" recipes, one which contains all the
policy changes that meta-oe wishes to make compared to what's in
oe-core, and one which is a sort of "oe-core-next", containing changes
which are theoretically candidates for merging into oe-core but for
whatever reason are not quite ready to submit.
p.
next prev parent reply other threads:[~2012-05-17 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 9:32 [PATCH] Revert "kmod: Use base_libdir for installing libkmod" Koen Kooi
2012-05-15 20:54 ` Khem Raj
2012-05-17 20:29 ` Richard Purdie
2012-05-17 20:44 ` Koen Kooi
2012-05-17 21:02 ` Richard Purdie
2012-05-17 21:16 ` Tom Rini
2012-05-17 21:25 ` Paul Eggleton
2012-05-17 21:51 ` Otavio Salvador
2012-05-17 22:01 ` Paul Eggleton
2012-05-17 22:11 ` Otavio Salvador
2012-05-17 22:21 ` Paul Eggleton
2012-05-17 22:22 ` Phil Blundell [this message]
2012-05-17 22:50 ` Khem Raj
2012-05-17 23:00 ` Andreas Müller
2012-05-18 6:19 ` Koen Kooi
2012-05-18 8:16 ` Koen Kooi
2012-05-18 7:52 ` Koen Kooi
2012-05-18 10:29 ` Richard Purdie
2012-05-18 10:37 ` Koen Kooi
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=1337293371.3181.190.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.