From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 0/3] Add mosh and dependencies
Date: Mon, 15 Jul 2013 16:36:36 +0100 [thread overview]
Message-ID: <5498122.1xgS5ZiCM9@helios> (raw)
In-Reply-To: <CAP9ODKp3=Lf7C710t8AeC+o9jA46oQFEokUiHuSW+L4W-uJFJA@mail.gmail.com>
On Monday 15 July 2013 12:02:59 Otavio Salvador wrote:
> On Mon, Jul 15, 2013 at 9:37 AM, Joe MacDonald
>
> <Joe.MacDonald@windriver.com> wrote:
> > [[oe] [meta-oe][PATCH 0/3] Add mosh and dependencies] On 13.07.13 (Sat
15:47) Paul Eggleton wrote:
> >> Add a recipe for mosh, and for dependencies migrate libio-pty-perl from
> >> OE-Classic and bring in protobuf from meta-virtualization.
> >>
> >> I considered putting this in meta-networking, however meta-virtualization
> >> will still need protobuf and it already depends on meta-oe, and
> >> officially meta-networking does not depend on meta-oe so splitting these
> >> would not really work with the current layer dependencies.
> >
> > That's not strictly true anymore, actually. It was my intent and I
> > think there's value in it, but CRDA (already in meta-networking) depends
> > on python-m2crypto (in meta-oe). I discovered it in my world build a
> > few weeks ago and hadn't yet managed to get round to seeing if there was
> > a clean way to separate the two.
> >
> > I absolutely don't want the stated intent that meta-networking be
> > standalone be a barrier to adding packages to it that clearly belong to
> > it.
> >
> > That's my way of saying I've no objection right now to including this in
> > meta-net.
>
> I agree; maybe we could add those inside meta-oe subdir? so people can
> opt in enable them or not.
Sorry Otavio, what are you suggesting exactly?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-15 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 14:47 [meta-oe][PATCH 0/3] Add mosh and dependencies Paul Eggleton
2013-07-13 14:47 ` [meta-oe][PATCH 1/3] protobuf: add recipe from meta-virtualization and tweak Paul Eggleton
2013-07-16 15:36 ` Samuel Stirtzel
2013-07-16 17:07 ` Paul Eggleton
2013-07-13 14:47 ` [meta-oe][PATCH 2/3] libio-pty-perl: add from OE-Classic and update Paul Eggleton
2013-07-13 14:47 ` [meta-oe][PATCH 3/3] mosh: add new recipe for version 1.2.4 Paul Eggleton
2013-07-15 3:54 ` Otavio Salvador
2013-07-15 9:40 ` Paul Eggleton
2013-07-15 12:37 ` [meta-oe][PATCH 0/3] Add mosh and dependencies Joe MacDonald
2013-07-15 15:02 ` Otavio Salvador
2013-07-15 15:36 ` Paul Eggleton [this message]
2013-07-15 16:40 ` Otavio Salvador
2013-07-15 17:42 ` Joe MacDonald
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=5498122.1xgS5ZiCM9@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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