From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 2/5] gdk-pixbuf: Add hicolor-icon-theme as RDEPENDS
Date: Sun, 11 Dec 2011 13:09:35 -0800 [thread overview]
Message-ID: <4EE51C0F.4020905@linux.intel.com> (raw)
In-Reply-To: <4C7FA566-48B4-4F91-B705-F3F7DB3D9082@dominion.thruhere.net>
On 12/11/2011 12:52 AM, Koen Kooi wrote:
>
> Op 10 dec. 2011, om 23:01 heeft Saul Wold het volgende geschreven:
>
>> Signed-off-by: Saul Wold<sgw@linux.intel.com>
>> ---
>> meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.24.0.bb | 4 ++++
>> 1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> +RDEPENDS = "hicolor-icon-theme"
>
> Are you sure this is the right place? gdk-pixbuf are just the image loaders, they shouldn't have a hard dependency on a bunch of icons... As for the apps, gtk-icon-cache.bbclass should be adding the hicolor dep automatically.
>
Your right, I did not look in the bbclass, I was trying to resolve this
issue:
Configuring gdk-pixbuf-loader-png.
gtk-update-icon-cache: No theme index file.
Configuring gdk-pixbuf-loader-jpeg.
gtk-update-icon-cache: No theme index file.
Configuring liberation-fonts.
Configuring gdk-pixbuf-loader-xpm.
gtk-update-icon-cache: No theme index file.
Configuring gdk-pixbuf-loader-gif.
gtk-update-icon-cache: No theme index file.
Which seems to stem from gdk-pixbuf-loader-xpm's postinstall trying to
cache the hicolor icons. I can see the dependency, but they did not
seem to be installed, more digging is required.
I withdraw this patch.
Sau!
> regards,
>
> Koen
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-12-11 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 22:01 [PATCH 0/5] Fixes related to self-hosted build Saul Wold
2011-12-10 22:01 ` [PATCH 1/5] ncurses: libcurses.so should link to libncurses.so Saul Wold
2011-12-10 22:01 ` [PATCH 2/5] gdk-pixbuf: Add hicolor-icon-theme as RDEPENDS Saul Wold
2011-12-11 8:52 ` Koen Kooi
2011-12-11 21:09 ` Saul Wold [this message]
2011-12-10 22:01 ` [PATCH 3/5] self-hosted: Add ext2 utilites and perl-pod for building Saul Wold
2011-12-10 23:24 ` Wolfgang Denk
2011-12-11 0:47 ` Saul Wold
2011-12-11 7:05 ` Paul Menzel
2011-12-11 20:17 ` Saul Wold
2011-12-10 22:02 ` [PATCH 4/5] texinfo: fix compile failure due target makedoc binary being used Saul Wold
2011-12-10 22:02 ` [PATCH 5/5] bitbake.conf: remove texinfo-native from ASSUME_PROVIDED Saul Wold
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=4EE51C0F.4020905@linux.intel.com \
--to=sgw@linux.intel.com \
--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