From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC} glib-2.0 cleanup
Date: Sun, 28 Feb 2010 21:05:23 +0100 [thread overview]
Message-ID: <hmeia3$p6c$1@dough.gmane.org> (raw)
In-Reply-To: <ac9c93b11002281139g6963e753w970c97002611c78c@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
How do you know that some versions aren't used at all? Did you check all
external overlays?
But more importantly, what harm do the recipes do to you? Does it offend
you that there are 26 recipes?
What are you trying to accomplish?
If a recipe isn't doing any harm, just leave it alone. Deleting recipes
just to please someones sense of aesthetics is the wrong thing to do.
What would be a lot better is to fix the latest version for each minor
release to use things like new style staging, bbclassextend, etc and
*after* that clean up ask to remove the recipes that weren't updated.
That way there is a recipe for each minor version so we can check
regressions quite easily. But the real bonus is that the remaining
recipes are of good quality. Your proposal doesn't address any QA
concerns, it just makes the mess a bit smaller.
And even then I would rather move recipe + associated patches to
obsolete than delete it. When we start doing tarball releases
recipes/obsolete will be a lot more important than it is now.
On 28-02-10 20:39, Frans Meulenbroeks wrote:
> We have 26 glib-2.0 recipes (and 8 native ones). (see ls below)
> Only a few versions are used (see also the grep below)
>
> for glib-2.0:
> "2.12.12"
> "2.16.4"
> "2.18.3"
> "2.20.3"
> "2.22.1"
> "2.22.4"
> "2.6.4"
> "2.8.6"
>
> for glib-2.0-native:
> "2.16.1"
> "2.18.0"
> "2.22.1"
> "2.22.4"
>
> Both include the last two versions
> Proposal is to remove all versions that are not used.
>
> How do people feel about this?
>
> Frans
>
>
> frans@linux-suse:~/oe/openembedded/recipes/glib-2.0> ls
> bug-556515.patch glib-2.0-2.16.3 glib-2.0-native_2.12.4.bb
> glib-2.0_2.12.13.bb glib-2.0_2.18.1.bb
> files glib-2.0-2.16.4 glib-2.0-native_2.16.1.bb
> glib-2.0_2.12.6.bb glib-2.0_2.18.3.bb
> glib-2.0-2.12.10 glib-2.0-2.16.5 glib-2.0-native_2.18.0.bb
> glib-2.0_2.12.9.bb glib-2.0_2.2.3.bb
> glib-2.0-2.12.11 glib-2.0-2.18.0 glib-2.0-native_2.2.3.bb
> glib-2.0_2.14.0.bb glib-2.0_2.20.3.bb
> glib-2.0-2.12.12 glib-2.0-2.18.1 glib-2.0-native_2.22.1.bb
> glib-2.0_2.14.1.bb glib-2.0_2.20.4.bb
> glib-2.0-2.12.13 glib-2.0-2.18.3 glib-2.0-native_2.4.6.bb
> glib-2.0_2.14.4.bb glib-2.0_2.22.1.bb
> glib-2.0-2.12.9 glib-2.0-2.2.3 glib-2.0-native_2.6.5.bb
> glib-2.0_2.15.6.bb glib-2.0_2.22.4.bb
> glib-2.0-2.14.0 glib-2.0-2.20.3 glib-2.0-native_2.6.6.bb
> glib-2.0_2.16.1.bb glib-2.0_2.4.6.bb
> glib-2.0-2.14.1 glib-2.0-2.20.4 glib-2.0.inc
> glib-2.0_2.16.3.bb glib-2.0_2.6.4.bb
> glib-2.0-2.14.4 glib-2.0-2.22.1 glib-2.0_2.12.10.bb
> glib-2.0_2.16.4.bb glib-2.0_2.6.6.bb
> glib-2.0-2.15.6 glib-2.0-2.22.4 glib-2.0_2.12.11.bb
> glib-2.0_2.16.5.bb glib-2.0_2.8.6.bb
> glib-2.0-2.16.1 glib-2.0-native-2.12.4 glib-2.0_2.12.12.bb
> glib-2.0_2.18.0.bb glib.inc
> frans@linux-suse:~/oe/openembedded/recipes/glib-2.0> grep PREFERENCE *
> glib-2.0_2.16.3.bb:DEFAULT_PREFERENCE = "-1"
> glib-2.0_2.16.4.bb:DEFAULT_PREFERENCE = "-1"
> glib-2.0_2.16.5.bb:DEFAULT_PREFERENCE = "-1"
> frans@linux-suse:~/oe/openembedded/recipes/glib-2.0> grep -r glib-2.0 ../../conf
> ../../conf/distro/micro.conf:USE_NLS_glib-2.0 = "yes"
> ../../conf/distro/micro.conf:USE_NLS_glib-2.0-native = "yes"
> ../../conf/distro/chinook-compat.conf:PREFERRED_VERSION_glib-2.0
> = "2.12.12"
> ../../conf/distro/chinook-compat.conf:PKG_glib-2.0 = "libglib2.0-0"
> ../../conf/distro/maemo5-compat.conf:PREFERRED_VERSION_glib-2.0
> = "2.20.3"
> ../../conf/distro/maemo5-compat.conf:PKG_glib-2.0 = "libglib2.0-0"
> ../../conf/distro/include/angstrom-2008-preferred-versions.inc:PREFERRED_VERSION_glib-2.0
> = "2.22.4"
> ../../conf/distro/include/angstrom-2008-preferred-versions.inc:PREFERRED_VERSION_glib-2.0-native
> = "2.22.4"
> ../../conf/distro/include/kaeilos-2009-preferred-versions.inc:PREFERRED_VERSION_glib-2.0
> = "2.22.4"
> ../../conf/distro/include/kaeilos-2009-preferred-versions.inc:PREFERRED_VERSION_glib-2.0-native
> = "2.22.4"
> ../../conf/distro/include/preferred-gpe-versions-2.7.inc:PREFERRED_VERSION_glib-2.0
> ?= "2.6.4"
> ../../conf/distro/include/angstrom-uclibc.inc:USE_NLS_glib-2.0 = "yes"
> ../../conf/distro/include/angstrom-uclibc.inc:USE_NLS_glib-2.0-native = "yes"
> ../../conf/distro/include/sane-toolchain-uclinux-uclibc.inc:USE_NLS_glib-2.0
> = "yes"
> ../../conf/distro/include/sane-toolchain-uclinux-uclibc.inc:USE_NLS_glib-2.0-native
> = "yes"
> ../../conf/distro/include/preferred-om-2008-versions.inc:PREFERRED_VERSION_glib-2.0
> ?= "2.16.4"
> ../../conf/distro/include/preferred-om-2008-versions.inc:PREFERRED_VERSION_glib-2.0-native
> ?= "2.16.1"
> ../../conf/distro/include/slugos.inc:# glib-2.0 builds require USE_NLS
> to be overridden
> ../../conf/distro/include/slugos.inc:USE_NLS_glib-2.0 = "yes"
> ../../conf/distro/include/slugos.inc:USE_NLS_glib-2.0-native = "yes"
> ../../conf/distro/include/preferred-shr-versions.inc:PREFERRED_VERSION_glib-2.0
> = "2.22.4"
> ../../conf/distro/include/preferred-shr-versions.inc:PREFERRED_VERSION_glib-2.0-native
> = "2.22.4"
> ../../conf/distro/include/preferred-slugos-versions.inc:PREFERRED_VERSION_glib-2.0 ?=
> "2.22.1"
> ../../conf/distro/include/preferred-slugos-versions.inc:PREFERRED_VERSION_glib-2.0-native ?=
> "2.22.1"
> ../../conf/distro/include/preferred-om-2009-versions.inc:PREFERRED_VERSION_glib-2.0
> = "2.18.3"
> ../../conf/distro/include/preferred-om-2009-versions.inc:PREFERRED_VERSION_glib-2.0-native
> = "2.18.0"
> ../../conf/distro/include/angstrom-uclinux-uclibc.inc:USE_NLS_glib-2.0 = "yes"
> ../../conf/distro/include/angstrom-uclinux-uclibc.inc:USE_NLS_glib-2.0-native
> = "yes"
> ../../conf/distro/include/maemo-preferred.inc:PREFERRED_VERSION_glib-2.0
> = "2.6.4"
> ../../conf/distro/include/preferred-gpe-versions-2.8.inc:PREFERRED_VERSION_glib-2.0
> ?= "2.8.6"
> ../../conf/distro/include/sane-toolchain-uclibc.inc:USE_NLS_glib-2.0 = "yes"
> ../../conf/distro/include/sane-toolchain-uclibc.inc:USE_NLS_glib-2.0-native
> = "yes"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLisyDMkyGM64RGpERAldgAKCM3/TP7G540bPars60N9AF9Vcr1QCfe2rR
QHQjbqauqjmMMvFXz5uhNCI=
=BPJk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-28 20:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 19:39 [RFC} glib-2.0 cleanup Frans Meulenbroeks
2010-02-28 20:05 ` Koen Kooi [this message]
2010-02-28 20:26 ` Frans Meulenbroeks
2010-02-28 21:40 ` Graham Gower
2010-03-01 15:15 ` Denys Dmytriyenko
2010-03-01 15:20 ` Frans Meulenbroeks
2010-03-01 15:25 ` Marcin Juszkiewicz
2010-03-06 19:36 ` Frans Meulenbroeks
2010-02-28 21:35 ` Michael 'Mickey' Lauer
2010-03-01 7:30 ` Frans Meulenbroeks
2010-03-01 14:35 ` Koen Kooi
2010-03-01 14:43 ` Dr. Michael Lauer
2010-03-01 15:02 ` bitbake -b with BBCLASSEXTENDed recipes Was: " Martin Jansa
2010-03-15 16:48 ` bitbake -b with BBCLASSEXTENDed recipes Enrico Scholz
2010-03-16 3:23 ` Denys Dmytriyenko
2010-03-17 8:48 ` Martin Jansa
2010-03-17 10:03 ` Enrico Scholz
2010-03-01 22:11 ` [RFC} glib-2.0 cleanup Khem Raj
2010-03-01 22:30 ` Denys Dmytriyenko
2010-03-01 22:34 ` Chris Larson
2010-03-01 22:49 ` Khem Raj
2010-03-01 22:51 ` Chris Larson
2010-03-01 23:04 ` Khem Raj
2010-03-01 23:26 ` Chris Larson
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='hmeia3$p6c$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.