From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] recipes-efl inside meta-oe or meta-efl next to meta-oe?
Date: Thu, 24 Mar 2011 10:50:25 +0000 [thread overview]
Message-ID: <1300963825.2752.3.camel@scimitar> (raw)
In-Reply-To: <20110324074926.GR2224@xora-desktop.xora.org.uk>
On Thu, 2011-03-24 at 07:49 +0000, Graeme Gregory wrote:
> On Thu, Mar 24, 2011 at 12:27:28AM +0000, Richard Purdie wrote:
> > Have either of you ever tried to explain some of the concepts we're
> > dealing with to people who aren't deeply engaged engineers?
> >
> Yes, everytime I apply for a new job/contract getting quite used to
> explaining it.
>
> > Having a model showing the kinds of things layers can do is extremely
> > helpful in explaining the concept to people.
> >
> > Part of OE's problem and the number one complaint about it is that its
> > hard to understand. If as I/others try and put things into terms that
> > others can understand get undermined with this kind of response its just
> > going to further the impression that OE is nice but never going to be
> > useful in the real world.
> >
> > As for whether that diagram is practical, I actually believe it is in
> > some cases, like the one I described above. Certainly not all but its
> > worth trying to strive to simplify and make things fit simpler models
> > if/when we can. If we don't even bother trying, there is no chance
> > things will improve.
> >
>
> You miss my point, Joshua's email reads to me like "our goal is to make OE
> like this diagram" which if true would cripple OE to being incredibly simple
> and non flexible.
It certainly wasn't my intention to imply that, in fact the "me too"
strongly indicates that I agreed with you and that I personally thought
the diagram was a useful *aide* in explaining layers.
>
> My vision of a seperated out OE is to seperate components out into logical
> boxes. Ie the gnome box, the kde box, the xorg box. Then like we used to do
> with our lego or mecheno sets. When we want to build something we know what
> components we want so we select the boxes that contain those components.
FWIW, this is the same vision I was already agreeing with.
Regards,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-24 10:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 11:49 [RFC] recipes-efl inside meta-oe or meta-efl next to meta-oe? Koen Kooi
2011-03-23 12:02 ` Otavio Salvador
2011-03-23 12:24 ` Richard Purdie
2011-03-23 12:31 ` Graeme Gregory
2011-03-23 15:19 ` Khem Raj
2011-03-23 15:33 ` Koen Kooi
2011-03-24 4:26 ` Khem Raj
[not found] ` <20110323153311.GG3418@jama.jama.net>
2011-03-23 15:39 ` Koen Kooi
[not found] ` <20110323164609.GI3418@jama.jama.net>
2011-03-23 18:05 ` Koen Kooi
2011-03-23 15:39 ` Richard Purdie
2011-03-23 15:42 ` Koen Kooi
2011-03-23 16:27 ` Richard Purdie
2011-03-23 15:40 ` Graeme Gregory
2011-03-23 16:03 ` Joshua Lock
2011-03-23 17:52 ` Graeme Gregory
2011-03-23 23:02 ` Richard Purdie
2011-03-23 23:53 ` Graeme Gregory
2011-03-23 23:57 ` Philip Balister
2011-03-24 0:27 ` Richard Purdie
2011-03-24 7:49 ` Graeme Gregory
2011-03-24 10:00 ` Koen Kooi
2011-03-24 10:26 ` Graeme Gregory
2011-03-24 10:54 ` Richard Purdie
2011-03-24 10:50 ` Joshua Lock [this message]
2011-03-24 2:56 ` Khem Raj
2011-03-23 16:51 ` Richard Purdie
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=1300963825.2752.3.camel@scimitar \
--to=josh@linux.intel.com \
--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.