From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] glib-2.0: remove old glib-2.0-native recipes
Date: Thu, 08 Apr 2010 15:50:37 -0700 [thread overview]
Message-ID: <1270767037.29304.40.camel@trini-m4400> (raw)
In-Reply-To: <4BBE4B91.40602@mwester.net>
On Thu, 2010-04-08 at 16:33 -0500, Mike Westerhof wrote:
> Antonio Ospite wrote:
> > Having these around can cause some conflict in recipes depending on
> > recent glib-2.0-native, see [1].
> >
> > What can happen is that, when no preferred versions are set (like in
> > DISTRO=minimal), bitbake picks up an older -native recipe even if a more
> > recent one using the BBCLASSEXTEND = "native" mechanism exists.
> >
> > [1] http://tinderbox.openembedded.org/packages/540390/
> >
> > Signed-off-by: Antonio Ospite <ospite@studenti.unina.it>
> > ---
> > Please check if the commit message is clear enough, I think I've figured
> > out what's happening behind the scenes, but I have not that deep
> > knowledge of bitbake.
> >
> > Thanks,
> > Antonio Ospite
> > http://ao2.it
> >
> >
> > .../glib-gettextize-dir.patch | 11 --
> > recipes/glib-2.0/glib-2.0-native_2.12.4.bb | 49 ----------
> > recipes/glib-2.0/glib-2.0-native_2.16.1.bb | 40 --------
> > recipes/glib-2.0/glib-2.0-native_2.18.0.bb | 40 --------
> > recipes/glib-2.0/glib-2.0-native_2.2.3.bb | 100 --------------------
> > recipes/glib-2.0/glib-2.0-native_2.22.1.bb | 39 --------
> > recipes/glib-2.0/glib-2.0-native_2.4.6.bb | 49 ----------
> > recipes/glib-2.0/glib-2.0-native_2.6.5.bb | 51 ----------
> > recipes/glib-2.0/glib-2.0-native_2.6.6.bb | 51 ----------
> > 9 files changed, 0 insertions(+), 430 deletions(-)
> > delete mode 100644 recipes/glib-2.0/glib-2.0-native-2.12.4/glib-gettextize-dir.patch
> > delete mode 100644 recipes/glib-2.0/glib-2.0-native_2.12.4.bb
> > delete mode 100644 recipes/glib-2.0/glib-2.0-native_2.16.1.bb
> > delete mode 100644 recipes/glib-2.0/glib-2.0-native_2.18.0.bb
> > delete mode 100644 recipes/glib-2.0/glib-2.0-native_2.2.3.bb
> > delete mode 100644 recipes/glib-2.0/glib-2.0-native_2.22.1.bb
>
> NACK. This glib version is still in use; don't delete it:
> /u/slug/slugos/tmp/work/x86_64-linux/glib-2.0-native-2.22.1-r6.2
>
> (Surely there must a better way to fix this than removal of active recipes?)
If 2.22.1 was converted to BBCLASSEXTEND, the rest of the mechanisms
would work right again.
--
Tom Rini <tom_rini@mentor.com>
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-04-08 22:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 15:17 gtk+-native-2.20.0-r8.0 fails in do_configure Antonio Ospite
2010-04-03 18:17 ` Marcin Juszkiewicz
2010-04-06 9:58 ` Antonio Ospite
2010-04-08 9:22 ` Antonio Ospite
2010-04-08 9:54 ` Koen Kooi
2010-04-08 14:21 ` Antonio Ospite
2010-04-08 21:20 ` [PATCH] glib-2.0: remove old glib-2.0-native recipes Antonio Ospite
2010-04-08 21:33 ` Mike Westerhof
2010-04-08 22:50 ` Tom Rini [this message]
2010-04-09 7:51 ` Koen Kooi
2010-04-09 10:32 ` Michael 'Mickey' Lauer
2010-04-09 19:21 ` Antonio Ospite
2010-04-08 14:11 ` gtk+-native-2.20.0-r8.0 fails in do_configure Antonio Ospite
2010-04-08 14:15 ` Koen Kooi
2010-04-08 14:25 ` Antonio Ospite
2010-04-08 15:55 ` Koen Kooi
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=1270767037.29304.40.camel@trini-m4400 \
--to=tom_rini@mentor.com \
--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