From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gnome.bbclass
Date: Fri, 24 Aug 2012 10:35:57 +0200 [thread overview]
Message-ID: <k17eda$nmn$1@ger.gmane.org> (raw)
In-Reply-To: <CAJTo0LbmhE+cLgJn2nxcdbj1dVH+5Y8xaT1tgP7FPtBspmLFtg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 23-08-12 23:32, Burton, Ross schreef:
> On 23 August 2012 10:35, Martin Jansa <martin.jansa@gmail.com> wrote:
>> git log says it was because of 'hicolor-icon-theme-native' and
>> 'gnome-common-native'
>
> Isn't that quite a sledgehammer approach, why couldn't BBCLASSEXTEND +=
> "native" be added to just those two recipes?
With the current tiny set of gnome recipes, only those 2 needed it. In
OE-classic with a lot more gnome a lot more was needed. Over time the gnome
cleaned up their act as well.
KDE on the other hand....
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFQNzzsMkyGM64RGpERArH0AJ4jfChjl+AYJtk+F3dkzIp7yhY9RgCeIWN0
xtyRNgSW6v8z0jkm43GKbYA=
=ozoX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-08-24 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 9:22 gnome.bbclass Andreas Müller
2012-08-23 9:35 ` gnome.bbclass Martin Jansa
2012-08-23 21:32 ` gnome.bbclass Burton, Ross
2012-08-24 8:35 ` Koen Kooi [this message]
2012-08-24 9:19 ` gnome.bbclass Samuel Stirtzel
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='k17eda$nmn$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.