Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gconf.bbclass: don't register schemas in the install stage
Date: Thu, 28 Jun 2012 18:10:52 -0400	[thread overview]
Message-ID: <1340921452.3482.3.camel@lenny> (raw)
In-Reply-To: <C4D2E4A76F2943CD9278FA15BFD5C15E@intel.com>

On Wed, 2012-06-27 at 07:01 +0100, Ross Burton wrote:

> I'd prefer to use an option that the GConf autoconf macro provides
> over patching every module that uses GConf, 

I wasn't objecting to your patch.  However, please do *also* (in
addition, as well, etc. ;) ) consider patching these modules upstream.

Concretely doing so will also fix jhbuild (and my gnome-ostree build
system).





  reply	other threads:[~2012-06-28 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 10:10 [PATCH] gconf.bbclass: don't register schemas in the install stage Ross Burton
2012-06-26 21:02 ` Colin Walters
2012-06-27  6:01   ` Ross Burton
2012-06-28 22:10     ` Colin Walters [this message]
2012-06-28 17:14 ` Saul Wold

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=1340921452.3482.3.camel@lenny \
    --to=walters@verbum.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