From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled
Date: Wed, 22 Feb 2012 15:00:28 +0000 [thread overview]
Message-ID: <3560864.DXtqnyRg82@helios> (raw)
In-Reply-To: <4F450191.20609@opendreambox.org>
On Wednesday 22 February 2012 15:54:09 Andreas Oberritter wrote:
> Nevertheless, I understand that 'x11' isn't appropriate. The upside of
> using 'x11' was that it wouldn't break distributions, like new flags
> would do.
Incidentally, I sent an RFC patch yesterday to add a mechanism to make it
possible to add new DISTRO_FEATURES without breaking existing distro
configurations. So far I haven't had any comments.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-22 15:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 11:26 [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled Andreas Oberritter
2012-02-22 11:26 ` [PATCH 1/5] libsoup-2.4: don't depend on libgnome-keyring unless x11 is defined Andreas Oberritter
2012-02-22 12:56 ` Koen Kooi
2012-02-24 8:10 ` Khem Raj
2012-02-24 13:27 ` Andreas Oberritter
2012-02-24 15:05 ` Richard Purdie
2012-02-22 11:26 ` [PATCH 2/5] libproxy: don't depend on gconf " Andreas Oberritter
2012-02-22 12:57 ` Koen Kooi
2012-02-22 11:26 ` [PATCH 3/5] gconf.bbclass: don't add dependencies or hooks " Andreas Oberritter
2012-02-22 11:26 ` [PATCH 4/5] gtk-icon-cache.bbclass: " Andreas Oberritter
2012-02-22 11:26 ` [PATCH 5/5] gnomebase.bbclass: skip packages inheriting gnomebase " Andreas Oberritter
2012-02-22 13:31 ` [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled Richard Purdie
2012-02-22 14:54 ` Andreas Oberritter
2012-02-22 15:00 ` Paul Eggleton [this message]
2012-02-22 21:24 ` Richard Purdie
2012-02-23 1:35 ` Andreas Oberritter
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=3560864.DXtqnyRg82@helios \
--to=paul.eggleton@linux.intel.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