From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 0/3] Add mosh and dependencies
Date: Mon, 15 Jul 2013 08:37:59 -0400 [thread overview]
Message-ID: <20130715123759.GB3842@windriver.com> (raw)
In-Reply-To: <cover.1373726565.git.paul.eggleton@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
[[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.
-J.
>
>
> The following changes since commit c383d6230942bb1558cee02764bced09031cb70f:
>
> llvm3.3: Add zlib dependency and explicitly enable it (2013-07-12 12:12:09 +0200)
>
> are available in the git repository at:
>
> git://git.openembedded.org/meta-openembedded-contrib paule/mosh
> http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/mosh
>
> Paul Eggleton (3):
> protobuf: add recipe from meta-virtualization and tweak
> libio-pty-perl: add from OE-Classic and update
> mosh: add new recipe for version 1.2.4
>
> meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb | 29 ++++++++++++++++++++++
> .../recipes-devtools/perl/libio-pty-perl_1.10.bb | 14 +++++++++++
> .../recipes-devtools/protobuf/protobuf_2.4.1.bb | 20 +++++++++++++++
> 3 files changed, 63 insertions(+)
> create mode 100644 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb
> create mode 100644 meta-oe/recipes-devtools/perl/libio-pty-perl_1.10.bb
> create mode 100644 meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb
>
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-07-15 12: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 ` Joe MacDonald [this message]
2013-07-15 15:02 ` [meta-oe][PATCH 0/3] Add mosh and dependencies Otavio Salvador
2013-07-15 15:36 ` Paul Eggleton
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=20130715123759.GB3842@windriver.com \
--to=joe.macdonald@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox