Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] classes/[gnome|gnomebase|mime]: enhance gnome related classes
Date: Wed, 09 Nov 2011 10:35:47 +0000	[thread overview]
Message-ID: <1320834947.10843.161.camel@ted> (raw)
In-Reply-To: <0A7ED8DD-40A2-4E01-90A1-B2BB9849E500@dominion.thruhere.net>

On Wed, 2011-11-09 at 11:27 +0100, Koen Kooi wrote:
> Op 9 nov. 2011, om 10:37 heeft Richard Purdie het volgende geschreven:
> 
> > On Wed, 2011-11-09 at 10:27 +0100, Koen Kooi wrote:
> >> Op 9 nov. 2011, om 01:53 heeft Joshua Lock het volgende geschreven:
> >> 
> >>> This patch pulls in the gnome related classes from oe-core which
> >>> adds extra packaging rules and functionality whilst modularising things
> >>> so that one can get a subset of gnome functionality without adding a lot
> >>> of extra dependencies.
> >>> 
> >>> These aren't an exact copy of the classes from meta-openembedded, notable
> >>> differences are:
> >>> * gnome.bbclass - I dropped the BBCLASSEXTEND
> >> 
> >> It looks that will break a number of things in meta-oe, why was it dropped?
> > 
> > Unconditionally BBCLASSEXTENDing everything gnome is a great way to hack
> > around build issues and create a convoluted dependency mess that isn't
> > really required. I'd much rather we try and minimise the amount of
> > -native dependencies to those actually needed.
> > 
> > Comparing our builds against other systems its becoming clear our
> > convoluted dependency trees are one of the areas we don't do as well and
> > it hurts performance :(.
> 
> The list of -native needed in meta-gnome:
> 
> bison-native
> cairo-native
> docbook-utils-native
> flex-native
> gconf-native
> gdk-pixbuf-native
> glib-2.0-native
> gnome-doc-utils-native
> gobject-introspection-native
> gtk-doc-native
> icon-naming-utils-native
> intltool-native
> libffi-native
> libidl-native
> libxml-parser-perl-native
> orbit2-native
> pango-native
> perl-native
> popt-native
> python-native

Many of which are not gnome bbclass derived recipes. I therefore think
it makes sense to put the BBCLASSEXTEND in the recipes where its needed
and not the core class...

Cheers,

Richard




  reply	other threads:[~2011-11-09 10:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09  0:53 [PATCH 0/3] Switch to upstream GConf Joshua Lock
2011-11-09  0:53 ` [PATCH 1/3] shared-mime-info: package runtime data separately Joshua Lock
2011-11-18 12:20   ` Rainer Koenig
2011-11-23 21:45     ` Khem Raj
2011-11-23 21:59       ` Koen Kooi
2011-11-09  0:53 ` [PATCH 2/3] classes/[gnome|gnomebase|mime]: enhance gnome related classes Joshua Lock
2011-11-09  9:27   ` Koen Kooi
2011-11-09  9:37     ` Richard Purdie
2011-11-09 10:27       ` Koen Kooi
2011-11-09 10:35         ` Richard Purdie [this message]
2011-11-09 11:18           ` Koen Kooi
2011-11-09 20:20             ` Joshua Lock
2011-11-09 19:14     ` Joshua Lock
2011-11-09  0:53 ` [PATCH 3/3] gconf: add upstream GNOME gconf 3.2.3 and drop gconf-dbus Joshua Lock
2011-11-09 15:18   ` Richard Purdie
2011-11-10 12:26 ` [PATCH 0/3] Switch to upstream GConf Richard Purdie

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=1320834947.10843.161.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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