From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: Splitting meta-oe
Date: Thu, 26 Jan 2012 19:36:21 +0100 [thread overview]
Message-ID: <4F219D25.3050604@opendreambox.org> (raw)
In-Reply-To: <20120126161123.GD3747@jama.jama.net>
On 26.01.2012 17:11, Martin Jansa wrote:
> On Thu, Jan 26, 2012 at 03:45:52PM +0100, Frans Meulenbroeks wrote:
>> - and if a recipe is not well enough tested it should probably not end up
>> in meta-oe anyway (but better e.g. in meta-oe-next or meta-oe-new or
>> whatever you want to call the super bleeding edge version)
>
> How will Joe Average know that because of webkit-efl he should enable
> meta-efl-next (or
> oe-core-next-libsoup-development-version-alpha-centauri-edition layer)
> if he doesn't even know what's happening in layers he is
> using already (meta-efl for webkit-efl)?
I think libsoup is not a good example, because the specific version
doesn't live in meta-oe, but in meta-efl, which is fine IMO.
Being someone who's just in the process of moving a distribution from
OE-classic to OE-core + meta-oe, I've already been busy figuring out the
exact differences between recipes present in both layers. I'd welcome
any reduction in duplication and versions present in both layers.
Regards,
Andreas
next prev parent reply other threads:[~2012-01-26 18:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 12:48 Splitting meta-oe Paul Eggleton
2012-01-25 14:01 ` Frans Meulenbroeks
2012-01-25 14:10 ` Martin Jansa
2012-01-25 15:09 ` Paul Eggleton
2012-01-25 17:01 ` Enrico
2012-01-25 14:34 ` Philip Balister
2012-01-25 14:47 ` Paul Eggleton
2012-01-25 16:00 ` Philip Balister
2012-01-25 17:33 ` Frans Meulenbroeks
2012-01-25 17:51 ` Khem Raj
2012-01-26 9:02 ` Martin Jansa
2012-01-26 14:45 ` Frans Meulenbroeks
2012-01-26 16:11 ` Martin Jansa
2012-01-26 18:36 ` Andreas Oberritter [this message]
2012-01-26 20:04 ` Khem Raj
2012-01-25 17:41 ` Paul Eggleton
2012-01-25 17:57 ` Phil Blundell
[not found] ` <4F2069CC.7060409@balister.org>
2012-01-25 21:03 ` Phil Blundell
2012-01-25 22:12 ` Philip Balister
2012-01-25 17:49 ` Khem Raj
2012-01-25 18:39 ` Paul Eggleton
2012-01-25 23:28 ` Khem Raj
2012-02-01 10:07 ` Paul Eggleton
2012-02-01 10:33 ` Koen Kooi
2012-02-01 11:11 ` Otavio Salvador
2012-02-01 15:39 ` Koen Kooi
2012-02-05 14:58 ` 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=4F219D25.3050604@opendreambox.org \
--to=obi@opendreambox.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@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.