From: alexander.kanavin@linux.intel.com
To: "Martin Jansa" <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: qt4 moves out of oe-core - to meta-qt4, or to meta-oe?
Date: Thu, 12 Nov 2015 19:38:58 +0200 (EET) [thread overview]
Message-ID: <58904.10.252.13.130.1447349938.squirrel@linux.intel.com> (raw)
In-Reply-To: <20151112171915.GK2574@jama>
> There is already enough meta-oe bloat moved from oe-core:
>
> http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112665.html
>
> WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on glib-2.0, but
> it isn't a build dependency?
If increasing bloat is a problem, why do recipes in meta-oe need to be
maintained indefinitely? Old cruft can be dropped from meta-oe, just as it
is dropped from oe-core. Just ask the public if it's ok, set a timeframe,
and do it.
qt-mobility in particular has been dead for several years, and doesn't
even have official upstream tarballs anymore. Why spend time fixing it?
Alex
next prev parent reply other threads:[~2015-11-12 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 16:45 qt4 moves out of oe-core - to meta-qt4, or to meta-oe? alexander.kanavin
2015-11-12 17:03 ` Andreas Müller
2015-11-12 19:08 ` Paul Eggleton
2015-11-13 11:39 ` [oe] " Otavio Salvador
2015-11-13 11:46 ` Martin Jansa
2015-11-16 9:43 ` Alexander Kanavin
2015-11-16 10:07 ` Andreas Oberritter
2015-11-16 10:26 ` volunteers for meta-qt4 repo maintenance? Alexander Kanavin
2015-11-18 22:08 ` Paul Eggleton
2015-11-16 11:20 ` [oe] qt4 moves out of oe-core - to meta-qt4, or to meta-oe? Otavio Salvador
2015-11-16 11:23 ` Alexander Kanavin
2015-11-16 11:24 ` Otavio Salvador
2015-11-16 17:10 ` akuster808
2015-11-16 17:39 ` Mark Hatle
2015-11-12 17:19 ` Martin Jansa
2015-11-12 17:38 ` alexander.kanavin [this message]
2015-11-12 18:59 ` Martin Jansa
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=58904.10.252.13.130.1447349938.squirrel@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox