On Wed, Jan 8, 2014 at 10:32 PM, Martin Jansa <martin.ja...@gmail.com>wrote:
> On Wed, Jan 08, 2014 at 11:21:08PM +0000, Paul Eggleton wrote: > > > In my opinion... > > > > > > Personally I would be in favour of removing GTK+ and the GNOME UI from > > > the core and putting them in their own layer for all the same reasons I > > > think Qt should be in its own layer: > > > - a "basic" image doesn't need them > > > - we can have different layers to track separate major releases (as > with > > > qt3, qt4, and qt5) > > > > The trouble is, if you have no toolkit at all, how do you test that X > still > > works properly? The selection we have provides a single unit allowing us > to > > test the entire stack reasonably well without having to add anything > else. I > > think that's a valuable thing to have. > > By testing oe-core + layer with X. > > Everybody else is using oe-core + couple of other layers, why do we need > to make oe-core testable with X _in single_ layer? > > I'm not saying that oe-core should be tested with 30 layers like my > world build, but why cannot AB have special build which builds > > oe-core + meta-xorg + meta-gnome > > and runs some runtime QA tests on that and then some other build with > > oe-core + meta-python > > for piglit tests? > > Is it limitation of AB scripts for builds that they cannot fetch other > layers so they need everything glued together with combo-layer? I full agree here; this would be more in line of what we communicate to our users and layers being a good and nice way to modularize the system... -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
