From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: poky@yoctoproject.org
Subject: Re: Poky doesn't play nice with meta-oe
Date: Thu, 15 Mar 2012 15:24:34 +0000 [thread overview]
Message-ID: <1856275.4JdY7aZveN@helios> (raw)
In-Reply-To: <4F5B73E6.9040908@mlbassoc.com>
On Saturday 10 March 2012 08:31:50 Gary Thomas wrote:
> I wanted to do some experimenting with midori (a webkit based
> browser that is [arguably] better than web2) in my familiar Poky
> environment.
>...
> * Rebuild core-image-sato
> Lots of packages get rebuilt, down to GCC which has been updated
> to r27 from r22. I thought the poky meta "core" was tracking meta-oe
> and openembedded-core more closely than this.
I agree, this is not particularly desirable. We've discussed this in the OE
TSC and the agreement was that the toolchain bits currently in the meta-oe
layer itself will be moved out to a separate layer.
> Image will boot, but most things are broken, no X, no network, ...
That's not good :(
> It looks like the evil systemd has pervaded meta-oe (which IMO should
> be at least a DISTRO decision).
I agree, but there are others who think it should be switchable on a per-image
basis. I don't think it's going to be long before that's impossible however.
> I guess the only way I'll be able to test this in Poky, if at all,
> will be to only import the midori recipes and its dependencies, which
> there seem to be many.
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.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-15 15:24 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 [this message]
2012-04-20 16:01 ` Andrea Galbusera
2012-04-20 16:38 ` Paul Eggleton
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=1856275.4JdY7aZveN@helios \
--to=paul.eggleton@linux.intel.com \
--cc=gary@mlbassoc.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.