From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC} glib-2.0 cleanup
Date: Mon, 01 Mar 2010 17:30:55 -0500 [thread overview]
Message-ID: <20100301223055.GF15391@denix.org> (raw)
In-Reply-To: <19c1b8a91003011411p420a449dw3c03d03c6f5cec9a@mail.gmail.com>
On Mon, Mar 01, 2010 at 02:11:54PM -0800, Khem Raj wrote:
> On Sun, Feb 28, 2010 at 1:35 PM, Michael 'Mickey' Lauer
> <mickey@vanille-media.de> wrote:
> > Am Sonntag, den 28.02.2010, 20:39 +0100 schrieb Frans Meulenbroeks:
> >> 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?
> >
> > Sounds good to me, althoug I'd recommend not removing them but just
> > moving them out of sight, i.e. in an 'old' folder. That way we could
> > please both the lets-keep-everything-no-matter-how-rotten and also the
> > lets-strive-for-few-high-quality recipes.
> >
>
> FWIW I like the idea of having 'obsolete' recipes so moving them to
> recipes/obsolete may not be so bad.
+1 on this one, since we already have recipes/obsolete in BBMASK by default
and it will reduce parse time for obsoleted recipes. And git-mv does a nice
enough job of preserving commit history...
--
Denys
next prev parent reply other threads:[~2010-03-01 22:34 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
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 [this message]
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=20100301223055.GF15391@denix.org \
--to=denis@denix.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