From: alexander.kanavin@linux.intel.com
To: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: qt4 moves out of oe-core - to meta-qt4, or to meta-oe?
Date: Thu, 12 Nov 2015 18:45:34 +0200 (EET) [thread overview]
Message-ID: <58488.10.252.13.130.1447346734.squirrel@linux.intel.com> (raw)
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?
Alex
next reply other threads:[~2015-11-12 16:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 16:45 alexander.kanavin [this message]
2015-11-12 17:03 ` [OE-core] qt4 moves out of oe-core - to meta-qt4, or to meta-oe? Andreas Müller
2015-11-12 17:03 ` Andreas Müller
2015-11-12 19:08 ` [OE-core] " Paul Eggleton
2015-11-12 19:08 ` Paul Eggleton
2015-11-13 11:39 ` [OE-core] " Otavio Salvador
2015-11-13 11:39 ` [oe] " Otavio Salvador
2015-11-13 11:46 ` [OE-core] " Martin Jansa
2015-11-13 11:46 ` [oe] " Martin Jansa
2015-11-16 9:43 ` [OE-core] " Alexander Kanavin
2015-11-16 9:43 ` [oe] " Alexander Kanavin
2015-11-16 10:07 ` [OE-core] " Andreas Oberritter
2015-11-16 10:07 ` [oe] " Andreas Oberritter
2015-11-16 10:26 ` volunteers for meta-qt4 repo maintenance? Alexander Kanavin
2015-11-18 22:08 ` [OE-core] " Paul Eggleton
2015-11-18 22:08 ` Paul Eggleton
2015-11-16 11:20 ` [OE-core] qt4 moves out of oe-core - to meta-qt4, or to meta-oe? Otavio Salvador
2015-11-16 11:20 ` [oe] " Otavio Salvador
2015-11-16 11:23 ` [OE-core] " Alexander Kanavin
2015-11-16 11:23 ` [oe] " Alexander Kanavin
2015-11-16 11:24 ` [OE-core] " Otavio Salvador
2015-11-16 11:24 ` [oe] " Otavio Salvador
2015-11-16 17:10 ` [OE-core] " akuster808
2015-11-16 17:10 ` [oe] " akuster808
2015-11-16 17:39 ` [OE-core] " Mark Hatle
2015-11-16 17:39 ` [oe] " Mark Hatle
2015-11-12 17:19 ` [OE-core] " Martin Jansa
2015-11-12 17:19 ` Martin Jansa
2015-11-12 17:38 ` [OE-core] " alexander.kanavin
2015-11-12 17:38 ` alexander.kanavin
2015-11-12 18:59 ` [OE-core] " Martin Jansa
2015-11-12 18:59 ` Martin Jansa
2015-11-16 10:37 ` [OE-core] " Burton, Ross
2015-11-16 10:37 ` [oe] " Burton, Ross
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=58488.10.252.13.130.1447346734.squirrel@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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.