Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH 3/4] hicolor-icon-theme: don't inherit gnome
Date: Sat, 11 Jul 2009 19:26:18 +0200	[thread overview]
Message-ID: <h3ahvq$kv2$1@ger.gmane.org> (raw)
In-Reply-To: <200907110929.56270.marcin@juszkiewicz.com.pl>

On 11-07-09 09:29, Marcin Juszkiewicz wrote:
> Dnia sobota, 11 lipca 2009 o 09:05:34 Koen Kooi napisał(a):
>> On 11-07-09 02:37, Michael Smith wrote:
>>> inherit autotools instead, so the theme doesn't end up depending
>>> on gconf and gnome-common.
>>
>> NAK, it's dragging gnome for gtk-icon-cache.bbclass to update the
>> theme cache files, your change would break that.
>
> So maybe it should inherit autotools and gtk-icon-cache?

exactly




  reply	other threads:[~2009-07-11 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11  0:36 [PATCH 1/4] xf86-input-elographics: add 1.2.3 Michael Smith
2009-07-11  0:36 ` [PATCH 2/4] xf86-video-vesa: add 2.2.0 Michael Smith
2009-07-11  0:37   ` [PATCH 3/4] hicolor-icon-theme: don't inherit gnome Michael Smith
2009-07-11  0:37     ` [PATCH 4/4] xf86-video-intel: add 2.6.3 Michael Smith
2009-07-11  8:25       ` Phil Blundell
2009-07-11  7:05     ` [PATCH 3/4] hicolor-icon-theme: don't inherit gnome Koen Kooi
2009-07-11  7:29       ` Marcin Juszkiewicz
2009-07-11 17:26         ` Koen Kooi [this message]
2009-07-12 21:05       ` Michael Smith
2009-07-12 21:09         ` [PATCH v2] " Michael Smith
2009-07-13  7:26         ` [PATCH 3/4] " Koen Kooi
2009-07-11  8:24   ` [PATCH 2/4] xf86-video-vesa: add 2.2.0 Phil Blundell
2009-07-11  8:25 ` [PATCH 1/4] xf86-input-elographics: add 1.2.3 Phil Blundell

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='h3ahvq$kv2$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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