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] gtk-icon-cache bbclass: only add runtime dependencies on hicolor-icon-theme when installing icons
Date: Fri, 05 Aug 2011 14:19:19 +0100 [thread overview]
Message-ID: <1312550359.14274.104.camel@rex> (raw)
In-Reply-To: <ED5193A2-1D7E-4424-8B5B-FF755B56FFFC@kernel.crashing.org>
On Fri, 2011-08-05 at 07:42 -0500, Kumar Gala wrote:
> On Aug 5, 2011, at 1:51 AM, Koen Kooi wrote:
>
> >
> > Op 5 aug. 2011, om 08:44 heeft Koen Kooi het volgende geschreven:
> >
> >>
> >> Op 5 aug. 2011, om 07:48 heeft Koen Kooi het volgende geschreven:
> >>
> >>>
> >>> Op 5 aug. 2011, om 07:32 heeft Saul Wold het volgende geschreven:
> >>>
> >>>> On 08/04/2011 10:28 PM, Koen Kooi wrote:
> >>>>>
> >>>>> Op 5 aug. 2011, om 04:23 heeft Saul Wold het volgende geschreven:
> >>>>>
> >>>>>> On 08/01/2011 04:08 AM, Koen Kooi wrote:
> >>>>>>> Tested with gnome-icon-theme and libsoup recipes on angstrom.
> >>>>>>>
> >>>>>> But you did not test it against anything in oe-core, it has broken the build for connman-gnome and oprofileui, which use this bbclass.
> >>>>>>
> >>>>>> The oe-core gnome-icon-theme does not include this class.
> >>>>>>
> >>>>>> Please correct this.
> >>>>>>
> >>>>>> Processing task-base-extended...
> >>>>>> | error: Failed dependencies:
> >>>>>> | hicolor-icon-theme is needed by tasks-0.19-r0.armv5te
> >>>>>> | hicolor-icon-theme is needed by connman-gnome-0.5-r6.armv5te
> >>>>>> | hicolor-icon-theme is needed by oprofileui-server-0.0+git1+0c3c32fa754c1d0b70e65767ea7048914f776396-r4.armv5te
> >>>>>
> >>>>> So you found broken metadata. If tasks, connman-gnome and oprofileui-server need hicolor-icon-theme, they should list it in their RDEPENDS_${PN}. That is a seperate issue than what I fixed in the bbclass
> >>>>
> >>>> Koen, the gtk-icon-cache.bbclass did contain that RDEPENDS, which you removed
> >>>
> >>> It wasn't removed, it was changed to only add the dependency when needed, and by the looks of it it works.
> >>>
> >>> Does the following patch work for you?
> >>>
> >>> diff --git a/meta/classes/gtk-icon-cache.bbclass b/meta/classes/gtk-icon-cache.bbclass
> >>> index d9b5d1b..1e65e06 100644
> >>> --- a/meta/classes/gtk-icon-cache.bbclass
> >>> +++ b/meta/classes/gtk-icon-cache.bbclass
> >>> @@ -1,5 +1,8 @@
> >>> FILES_${PN} += "${datadir}/icons/hicolor"
> >>>
> >>> +# OE can't resolve RDEPENDS added thru the python code below, so make sure it has been built.
> >>> +DEPENDS += "hicolor-icon-theme"
> >>> +
> >>> # This could run on the host as icon cache files are architecture independent,
> >>> # but there is no gtk-update-icon-cache built natively.
> >>> gtk_icon_cache_postinst() {
> >>
> >>
> >> I can answer that myself: no, it will cause a dependency loop
> >
> >
> > And this one?
> >
> > +++ b/meta/classes/gtk-icon-cache.bbclass
> > @@ -1,5 +1,7 @@
> > FILES_${PN} += "${datadir}/icons/hicolor"
> >
> > +DEPENDS += "${@['hicolor-icon-theme', '']['${BPN}' == 'hicolor-icon-theme']}"
>
> This fixes my issue with core-image-sato on mpc8315
This looks right to me. Should I turn this into a commit or are you
waiting for some reason?
Cheers,
Richard
next prev parent reply other threads:[~2011-08-05 13:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 11:08 [PATCH] gtk-icon-cache bbclass: only add runtime dependencies on hicolor-icon-theme when installing icons Koen Kooi
2011-08-04 14:47 ` Saul Wold
2011-08-05 2:23 ` Saul Wold
2011-08-05 5:28 ` Koen Kooi
2011-08-05 5:32 ` Saul Wold
2011-08-05 5:48 ` Koen Kooi
2011-08-05 5:51 ` Chris Larson
2011-08-05 5:55 ` Koen Kooi
2011-08-05 7:00 ` Chris Larson
2011-08-05 7:16 ` Koen Kooi
2011-08-05 16:27 ` Richard Purdie
2011-08-05 17:34 ` Koen Kooi
2011-08-05 6:44 ` Koen Kooi
2011-08-05 6:51 ` Koen Kooi
2011-08-05 12:42 ` Kumar Gala
2011-08-05 13:19 ` Richard Purdie [this message]
2011-08-05 14:16 ` 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=1312550359.14274.104.camel@rex \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox