From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Eric Bénard" <eric@eukrea.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] hicolor-icon-theme: keep inherited dependencies
Date: Thu, 30 May 2013 11:49:00 +0100 [thread overview]
Message-ID: <1369910940.14887.295.camel@ted> (raw)
In-Reply-To: <20130530123230.78dab18a@e6520eb>
On Thu, 2013-05-30 at 12:32 +0200, Eric Bénard wrote:
> Le Thu, 30 May 2013 09:32:38 +0100,
> "Burton, Ross" <ross.burton@intel.com> a écrit :
>
> > On 30 May 2013 09:09, Martin Jansa <martin.jansa@gmail.com> wrote:
> > > Doesn't it depend now on something which isn't allarch? IIRC gnome.bbclass
> > > brings gconf.
> >
> > gnome.bbclass is an abomination and should be gutted. Yes, this will
> > mean the build dependencies are massive, and I can't see why this
> > recipe needs gnome.bbclass. Then again it doesn't need gtk-icon-cache
> > either as it doesn't actually have any icons in. I'd be interested in
> > seeing a buildhistory-diff between the current recipe and one with
> > both inherit gnome and DEPENDS="" removed.
> >
> when removing gnome I get the following error at install :
> DEBUG: Executing shell function do_install
> install: cannot create regular file
> `/scratch/setup-scripts/build/tmp-defaultsetup-eglibc-eglibc/work/all-oe-li\
> nux/hicolor-icon-theme/0.12-r1/image//usr/share/icons/hicolor': No such
> file or directory
I have a suspicion we really want a gnomebase inherit in the recipe
instead of gnome and that might solve serveral issues in one.
Cheers,
Richard
next prev parent reply other threads:[~2013-05-30 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 7:44 [PATCH 1/2] hicolor-icon-theme: keep inherited dependencies Eric Bénard
2013-05-30 7:44 ` [PATCH 2/2] gtk-icon-cache pixbufcache: add a clear dependency on gdk-pixbuf-native Eric Bénard
2013-05-30 8:09 ` [PATCH 1/2] hicolor-icon-theme: keep inherited dependencies Martin Jansa
2013-05-30 8:32 ` Burton, Ross
2013-05-30 10:32 ` Eric Bénard
2013-05-30 10:48 ` Eric Bénard
2013-05-30 10:49 ` Richard Purdie [this message]
2013-05-30 11:11 ` Eric Bénard
2013-05-30 11:51 ` Burton, Ross
2013-05-30 18:26 ` Burton, Ross
2013-05-30 19:14 ` Eric Bénard
2013-05-30 10:34 ` Eric Bénard
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=1369910940.14887.295.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=eric@eukrea.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