From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] hicolor-icon-theme 0.12: add BBCLASSEXTEND=native for xfce tools
Date: Thu, 10 Nov 2011 13:20:50 +0000 [thread overview]
Message-ID: <1320931250.1165.18.camel@ted> (raw)
In-Reply-To: <1320929044-13077-1-git-send-email-koen@dominion.thruhere.net>
On Thu, 2011-11-10 at 13:44 +0100, Koen Kooi wrote:
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> .../hicolor-icon-theme/hicolor-icon-theme_0.12.bb | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb b/meta/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb
> index 759c9d8..aeb89c9 100644
> --- a/meta/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb
> +++ b/meta/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb
> @@ -5,6 +5,8 @@ BUGTRACKER = "https://bugs.freedesktop.org/"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://COPYING;md5=f08a446809913fc9b3c718f0eaea0426"
>
> +BBCLASSEXTEND = "native"
> +
> SECTION = "unknown"
> inherit gnome allarch
This is interesting dilemma since this is an allarch recipe. What issue
were you seeing to need this? Could we add the allarch sysroot directory
to PATH to resolve this instead? We could add a PROVIDES
"hicolor-icon-theme-native" too...
Cheers,
Richard
next prev parent reply other threads:[~2011-11-10 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 12:44 [PATCH] hicolor-icon-theme 0.12: add BBCLASSEXTEND=native for xfce tools Koen Kooi
2011-11-10 13:20 ` Richard Purdie [this message]
2011-11-10 13:38 ` Koen Kooi
2011-11-10 18:56 ` Andreas Müller
2011-11-11 6:53 ` xfce4-dev-tools (was [OE-core] [PATCH] hicolor-icon-theme 0.12: add BBCLASSEXTEND=native for xfce tools) Andreas Müller
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=1320931250.1165.18.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@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.