From: Adrian Bunk <bunk@stusta.de>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] gtk-icon-cache.bbclass: Depends on gtk+3
Date: Thu, 20 Jun 2019 12:19:13 +0300 [thread overview]
Message-ID: <20190620091913.GD27107@localhost> (raw)
In-Reply-To: <07882a06-4c45-07aa-9696-8de4f86b8c0b@windriver.com>
On Thu, Jun 20, 2019 at 04:46:16PM +0800, Robert Yang wrote:
>...
> Maybe gtk+2 is out of date? Since gtk+4 is on the way, so I think that we
> need something like virtual/gtk to fix these problems totally?
GTK+2 is mostly obsolete.
I just checked the GTK4 sources, and there it is renamed to
gtk4-update-icon-cache. Based on that I would say that your
patch is actually fine at least for now.
> // Robert
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-06-20 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 8:15 [PATCH 0/4] meta: 4 fixes Robert Yang
2019-06-20 8:15 ` [PATCH 1/4] linux-dummy: Add do_compile_kernelmodules Robert Yang
2019-06-20 8:15 ` [PATCH 2/4] make-mod-scripts: Depends on bison-native Robert Yang
2019-06-20 8:15 ` [PATCH 3/4] update-alternatives.bbclass: run update-alternatives firstly in postinst script Robert Yang
2019-06-20 15:33 ` Richard Purdie
2019-06-21 9:20 ` Robert Yang
2019-06-20 8:15 ` [PATCH 4/4] gtk-icon-cache.bbclass: Depends on gtk+3 Robert Yang
2019-06-20 8:28 ` Adrian Bunk
2019-06-20 8:46 ` Robert Yang
2019-06-20 9:19 ` Adrian Bunk [this message]
2019-06-20 9:52 ` Alexander Kanavin
2019-06-20 9:58 ` Robert Yang
2019-06-20 13:53 ` Richard Purdie
2019-06-20 13:56 ` Burton, Ross
2019-06-21 9:48 ` Robert Yang
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=20190620091913.GD27107@localhost \
--to=bunk@stusta.de \
--cc=liezhi.yang@windriver.com \
--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