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 00/12] Recipe upgrades, fixes and additions
Date: Tue, 08 Nov 2011 14:18:03 +0000	[thread overview]
Message-ID: <1320761883.10843.40.camel@ted> (raw)
In-Reply-To: <cover.1320709417.git.josh@linux.intel.com>

On Mon, 2011-11-07 at 16:10 -0800, Joshua Lock wrote:
> All,
> 
> Here's a series of patches I developed whilst trying to play around with some
> Clutter based software.
> 
> The interesting pieces may be:
> Clutter 1.8 series recipes - do we want/need to keep clutter 1.6 around?
> Are we OK with continuing to namespace the clutter recipes by clutter
> version?

Yes, I think this makes sense.

> Gconf - I've pulled in GConf from upstream as the D-Bus backend is maintained
> there now. For this I pulled in the gnome-related classes from meta-oe as they
> simplified this recipe and I've been wanting to see them merged for some time.

I had to drop this patch as the gnome classes need a bit more work. I'd
like to get gconf resolved though.

> Pulseaudio - whilst adding a required build dependency I changed the recipe so
> that it doesn't require X unless the X11 distro feature is enabled.
> 

So I merged the series apart from the gnome class and gconf pieces.

Cheers,

Richard




  parent reply	other threads:[~2011-11-08 14:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  0:10 [PATCH 00/12] Recipe upgrades, fixes and additions Joshua Lock
2011-11-08  0:10 ` [PATCH 01/12] cogl: add cogl 1.8.0 recipe Joshua Lock
2011-11-08  0:10 ` [PATCH 02/12] clutter-1.8: add 1.8.0 Joshua Lock
2011-11-08  0:10 ` [PATCH 03/12] clutter-gst-1.8: add 1.4.2 for use with clutter 1.8 Joshua Lock
2011-11-08 16:10   ` Saul Wold
2011-11-08 16:30     ` Joshua Lock
2011-11-08 16:54       ` Saul Wold
2011-11-08 16:59         ` Joshua Lock
2011-11-08  0:10 ` [PATCH 04/12] clutter-gtk-1.8: add clutter-gtk 0.11.4 Joshua Lock
2011-11-08  0:10 ` [PATCH 05/12] mx: add mx toolkit 1.3.2 Joshua Lock
2011-11-08  0:10 ` [PATCH 06/12] classes/[gnome|gnomebase|mime]: merge meta-oe's enhance gnome related classes Joshua Lock
2011-11-08 14:05   ` Richard Purdie
2011-11-08 16:35     ` Joshua Lock
2011-11-08  0:10 ` [PATCH 07/12] gconf: add upstream GNOME gconf 3.2.3 and drop gconf-dbus Joshua Lock
2011-11-08  0:10 ` [PATCH 08/12] libcanberra: add libvorbis to DEPENDS Joshua Lock
2011-11-08  0:10 ` [PATCH 09/12] gypsy: fix packaging Joshua Lock
2011-11-08  0:10 ` [PATCH 10/12] connman: split scripts into separate package Joshua Lock
2011-11-08 14:17   ` Koen Kooi
2011-11-08  0:10 ` [PATCH 11/12] pulseaudio: make X11 dependencies optional and add gtk+ Joshua Lock
2011-11-08  0:10 ` [PATCH 12/12] contacts: fix packaging of icons Joshua Lock
2011-11-08 14:18 ` Richard Purdie [this message]
2011-11-08 15:48   ` [PATCH 00/12] Recipe upgrades, fixes and additions Saul Wold
2011-11-15 19:03   ` Saul Wold
2011-11-15 21:38     ` Richard Purdie
2011-11-15 21:48       ` Joshua Lock
2011-11-08 17:36 ` Saul Wold
2011-11-08 18:31   ` Joshua Lock

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=1320761883.10843.40.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