From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] recipes-efl inside meta-oe or meta-efl next to meta-oe?
Date: Wed, 23 Mar 2011 16:27:49 +0000 [thread overview]
Message-ID: <1300897669.3018.16.camel@rex> (raw)
In-Reply-To: <EEB43C23-7673-4F6B-86BA-B3C15C52C744@dominion.thruhere.net>
On Wed, 2011-03-23 at 16:42 +0100, Koen Kooi wrote:
> Op 23 mrt 2011, om 16:39 heeft Richard Purdie het volgende geschreven:
>
> > On Wed, 2011-03-23 at 08:19 -0700, Khem Raj wrote:
> >> On Wed, Mar 23, 2011 at 4:49 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >>> Hi,
> >>>
> >>> I'd like to import the EFL recipes Martin did from meta-shr into the meta-openembedded repo. Before I go bothering Martin about it, what would be the best place to put them?
> >>>
> >>> Inside meta-oe:
> >>>
> >>> meta-openembedded/
> >>> meta-oe/
> >>> recipes-efl
> >>
> >> Can efl we layered directly on top of oe-core ? i.e. without needing meta-oe
> >> in that case its better to be an independent layer. otherwise I would say put
> >> them under recipes-efl
> >
> > I'd hope that it would be possible to run it on top of oe-core, at least
> > for its basic components. If its not possible, I'd like to understand
> > why so we can see if its possible to fix it.
> >
> > Ultimately, we need to add some kind of layer dependency information
> > although we don't have an implementation of that yet.
>
> I;m currently usng a low-tech README for that:
>
> http://gitorious.org/angstrom/angstrom-layers/blobs/master/README
>
> would be nice to come up with something machine parse-able.
That's the plan, have something in README's for now and then improve the
infrastructure over time to automate it.
We could define a simple convention of something like this in
layer.conf:
LAYERNAMES += "thislayername:<optionalversion>"
LAYERREQUIRES := '${@oe.util.layerrequirements(["layerA:versionA", "layerb:versionB"])}'
but its just random ideas off the top of my head at the moment!
Cheers,
Richard
next prev parent reply other threads:[~2011-03-23 16:30 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 [this message]
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
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=1300897669.3018.16.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox