Hello, On Thu, Jan 9, 2014 at 4:32 AM, Koen Kooi <k...@dominion.thruhere.net>wrote:
> > Op 9 jan. 2014, om 01:32 heeft Martin Jansa <martin.ja...@gmail.com> het > volgende geschreven: > > > 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 have never seen a good explanation for that > > > 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? > > And e.g. meta-xorg could live inside the oe-core git repo if additional > git repos are too scary. Everyone using OE-Core/Poky in real world end using many GIT repositories so I don't think it is a problem. -- 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