From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] xserver_xorg-server: Change default to X.org modular server
Date: Sat, 11 Apr 2015 20:18:05 +0200 [thread overview]
Message-ID: <20150411201805.4bac425d@free-electrons.com> (raw)
In-Reply-To: <20150411181330.GL4221@free.fr>
Dear Yann E. MORIN,
On Sat, 11 Apr 2015 20:13:30 +0200, Yann E. MORIN wrote:
> I would not mind much doing the switch to the modular Xserver by
> default. But that would mean proper dependency propagation (i.e. C++).
I don't understand what you mean here.
> However, an alternative solution would be to remove the 'default' clause
> altogether from the choice:
>
> - if C++ is available, the modular Xserver is enabled by default,
> being the first option in the choice;
>
> - if C++ is not enabled, then KDrive is enabled, being the only option
> in the choice.
Well, Bernd's patch is doing that in a perfectly fine way. If C++ is
available, the default on modular will work. If C++ is not available,
since the modular option will not be available, the only remaining
option in the choice will be Kdrive, and it will be the selected option.
Am I missing something?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-11 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 17:13 [Buildroot] [PATCH v2 1/1] xserver_xorg-server: Change default to X.org modular server Bernd Kuhls
2015-04-11 17:58 ` Thomas Petazzoni
2015-04-11 18:13 ` Yann E. MORIN
2015-04-11 18:18 ` Thomas Petazzoni [this message]
2015-04-11 18:35 ` Yann E. MORIN
2015-04-13 23:09 ` Arnout Vandecappelle
2015-04-11 18:19 ` Bernd Kuhls
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=20150411201805.4bac425d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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