From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Steve Sakoman <steve@sakoman.com>
Subject: Re: [PATCH RFC v2] gtk-icon-cache.bbclass: add -f option to gtk-update-icon-cache in postinst
Date: Wed, 11 Jan 2012 22:28:19 -0800 [thread overview]
Message-ID: <4F0E7D83.5050707@linux.intel.com> (raw)
In-Reply-To: <1325911915-16001-3-git-send-email-steve@sakoman.com>
On 01/06/2012 08:51 PM, Steve Sakoman wrote:
> The gtk-update-icon-cache utility does not create a cache file if
> one does not already exist. Since some packages (notably gnome-icon-theme)
> do not ship a cache file by default, the results of the utility are
> not saved. Adding the force option writes out the cache even if there
> wasn't a default cache in the package.
>
> Signed-off-by: Steve Sakoman<steve@sakoman.com>
> ---
> meta/classes/gtk-icon-cache.bbclass | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/gtk-icon-cache.bbclass b/meta/classes/gtk-icon-cache.bbclass
> index eac3061..0204fd3 100644
> --- a/meta/classes/gtk-icon-cache.bbclass
> +++ b/meta/classes/gtk-icon-cache.bbclass
> @@ -14,7 +14,7 @@ GDK_PIXBUF_MODULEDIR=${libdir}/gdk-pixbuf-2.0/2.10.0/loaders gdk-pixbuf-query-lo
>
> for icondir in /usr/share/icons/* ; do
> if [ -d $icondir ] ; then
> - gtk-update-icon-cache -qt $icondir
> + gtk-update-icon-cache -fqt $icondir
> fi
> done
> }
Seemed reasonable, so merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-01-12 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 4:51 [PATCH RFC v2] gtk-icon-cache.bbclass: add -f option to gtk-update-icon-cache in postinst Steve Sakoman
2012-01-12 6:28 ` Saul Wold [this message]
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=4F0E7D83.5050707@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
/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