[OE-core] [oe] qt4 moves out of oe-core - to meta-qt4, or to meta-oe?

Martin Jansa martin.jansa at gmail.com
Fri Nov 13 11:46:17 UTC 2015


On Fri, Nov 13, 2015 at 09:39:15AM -0200, Otavio Salvador wrote:
> On Thu, Nov 12, 2015 at 5:08 PM, Paul Eggleton
> <paul.eggleton at linux.intel.com> wrote:
> > On Thursday 12 November 2015 18:03:27 Andreas Müller wrote:
> >> On Thu, Nov 12, 2015 at 5:45 PM,  <alexander.kanavin at linux.intel.com> wrote:
> >> > Hello,
> >> >
> >> > now that 2.0 is out, it's time to move the Qt4 recipes out of oe-core.
> >> > This has been discussed previously here:
> >> > http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106355
> >> > .html
> >> >
> >> > I'm not sure where the recipes should land, and want to ask your opinion.
> >> > The options are:
> >> > 1) Make a new layer, meta-qt4, under meta-openembedded tree. Move also
> >> > everything in meta-oe/recipes-qt (and possibly other spots) to that layer.
> >> > This is somewhat more disruptive to people's layer configurations, but
> >> > would clearly separate qt4, and slim down meta-oe.
> >> >
> >> > 2) Simply move the qt4 recipes from oe-core to meta-oe/recipes-qt, so they
> >> > will be next to all the qt4-based software. This is less disruptive, but
> >> > adds bloat to meta-oe.
> >> >
> >> > Preferences?
> >>
> >> 1) or even better in a separate repo
> >
> > To be honest, I had anticipated this being a separate meta-qt4 repo myself. It
> > would be consistent with what has been done with Qt 5 and much earlier with
> > Qt 3.
> 
> Agreed.

I'm also fine with separate layer.

Even better for me, I'll be less tempted to include it in my world
builds and to fix qt-mobility-* issues.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20151113/3265b513/attachment-0002.sig>


More information about the Openembedded-core mailing list