Poky doesn't play nice with meta-oe

[Gary Thomas <gary@mlbassoc.com>]

I wanted to do some experimenting with midori (a webkit based
browser that is [arguably] better than web2) in my familiar Poky
environment.  I've run midori in the past by cobbling in the
recipes and dependencies, but I wanted to see if I could just
use the whole meta-oe layer, as is.  Here's what I tried:

* Build core-image-sato for qemuarm from latest master
   Everything works as expected

* Add in meta-oe layers, in particular (I used my up-to-date checkout
   of Angstrom for this):
     /local/new-angstrom/sources/meta-openembedded/meta-xfce \
     /local/new-angstrom/sources/meta-openembedded/meta-multimedia \
     /local/new-angstrom/sources/meta-openembedded/meta-gpe \
     /local/new-angstrom/sources/meta-openembedded/meta-initramfs \
     /local/new-angstrom/sources/meta-openembedded/meta-efl \
     /local/new-angstrom/sources/meta-openembedded/meta-oe \
     /local/new-angstrom/sources/meta-openembedded/meta-gnome \

* 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.

   Image will boot, but most things are broken, no X, no network, ...

It looks like the evil systemd has pervaded meta-oe (which IMO should
be at least a DISTRO decision).

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.

Oh well, so much for my "simple" test.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------