From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Andrea Galbusera <gizero@gmail.com>, poky@yoctoproject.org
Subject: Re: Poky doesn't play nice with meta-oe
Date: Fri, 20 Apr 2012 17:38:11 +0100 [thread overview]
Message-ID: <74169790.jigKjBi9LZ@helios> (raw)
In-Reply-To: <CAC+thW26psx39QTFBUqXexPkxao8hk_D_nmrMhOis5+0Gdo3YQ@mail.gmail.com>
On Friday 20 April 2012 18:01:54 Andrea Galbusera wrote:
> On Thu, Mar 15, 2012 at 4:24 PM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > That's not an unreasonable approach for now. However we do really want to
> > tidy up meta-oe such that it doesn't do surprising things when you enable
> > it. Hopefully we will get a chance to make progress on this over the next
> > few months.
>
> Before starting to mess up things I'm asking if there is any relevant
> improvement on this side? I need a few recipes that are in meta-oe but
> not in poky/yocto (python-twisted, gpsd and a few more). Enabling
> meta-oe over my current edison environment would be nice to avoid
> manually importing those recipes with dependencies. Maybe master
> branch and upcoming 1.2 are expected to work better on this side?
No major progress as yet, I've been busy with things leading up to the 1.2
release; however once that's out the door there should be more time available
for improving meta-oe.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-20 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 15:31 Poky doesn't play nice with meta-oe Gary Thomas
2012-03-15 15:24 ` Paul Eggleton
2012-04-20 16:01 ` Andrea Galbusera
2012-04-20 16:38 ` Paul Eggleton [this message]
2012-04-20 17:15 ` Andrea Galbusera
2012-04-20 16:49 ` Tomas Frydrych
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=74169790.jigKjBi9LZ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=gizero@gmail.com \
--cc=poky@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.