From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: X11 as DISTRO_FEATURE
Date: Thu, 11 Aug 2011 15:16:27 +0100 [thread overview]
Message-ID: <1313072188.6733.134.camel@phil-desktop> (raw)
In-Reply-To: <20110811132703.GA29758@chargestorm.se>
On Thu, 2011-08-11 at 15:27 +0200, Anders Darander wrote:
> The opposite of objections, at least from me... This is something that
> I've wanted to do for a long time (but I never seem to get the time for
> it).
>
> Once again, I'm fighting against not only building X-related stuff, but
> also preventing it from leaking into my image...
I guess another solution to the leakiness would be to evacuate all the
X11 recipes to a separate layer (but still within the oe-core repo) so
that you could enable or disable them en masse.
p.
next prev parent reply other threads:[~2011-08-11 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 12:17 X11 as DISTRO_FEATURE Phil Blundell
2011-08-11 13:27 ` Anders Darander
2011-08-11 14:16 ` Phil Blundell [this message]
2011-08-11 14:19 ` 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=1313072188.6733.134.camel@phil-desktop \
--to=philb@gnu.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