From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: LAMP layer
Date: Thu, 28 Jun 2012 10:12:02 +0100 [thread overview]
Message-ID: <2414274.9vjeGA9Qqn@helios> (raw)
In-Reply-To: <CAMKF1srYsORnfcvaTh5H3LEf=rGWHv3JWPpvsFpW=8FjuwWaKg@mail.gmail.com>
On Wednesday 27 June 2012 11:01:09 Khem Raj wrote:
> On Wed, Jun 27, 2012 at 9:49 AM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > It's something I've been discussing with Joe MacDonald already. I think
> > it's an either-or situation - the recipes will not need to be in both
> > layers. People who want recipes from either or both layers should be able
> > to include the layers as needed.
>
> from my experience of deploying layers for others. Its quite a talk
> for folks to get it and on top if you have overlapping recipes they
> are not making life any easier. if we start using this kind of method, it
> sure will fume into chaos. I think layers should have some wholeness to them
> but at the same time they should be leveraging other layers to get
> functionality they need.
I agree completely - my intention is not to have any overlapping recipes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-28 9:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 14:05 LAMP layer Paul Eggleton
2012-06-27 14:26 ` Marcin Juszkiewicz
2012-06-27 15:22 ` Jack Mitchell
2012-06-27 15:57 ` Tomas Frydrych
2012-06-27 16:27 ` Paul Eggleton
2012-06-27 16:40 ` Jack Mitchell
2012-06-27 16:49 ` Paul Eggleton
2012-06-27 18:01 ` Khem Raj
2012-06-28 9:12 ` Paul Eggleton [this message]
2012-06-27 15:49 ` [yocto] " Khem Raj
2012-06-27 15:49 ` Khem Raj
2012-06-27 15:58 ` [yocto] " Paul Eggleton
2012-06-27 15:58 ` Paul Eggleton
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=2414274.9vjeGA9Qqn@helios \
--to=paul.eggleton@linux.intel.com \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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.