From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] legacy/xserver: add a legacy entry for xserver >= 1.19.0
Date: Thu, 26 Jan 2017 23:06:45 +0100 [thread overview]
Message-ID: <87efzpcw7e.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170126205915.GC3413@free.fr> (Yann E. MORIN's message of "Thu, 26 Jan 2017 21:59:15 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
>> > Hum, but then we have the BR2_PACKAGE_XSERVER_XORG_SERVER_AIGLX option
>> > defined in two different places, with two different prompts. Do we
>> > really want to do this?
>>
>> No we don't. We certainly don't want that changing some option (the server
>> version) suddenly creates a legacy option.
> My stake on this:
> - we must add a legacy entry for 1.18
Ok.
> - we must not add a legacy entry for AIGLX, because it is not yet
> legacy. It will turn legacy when the last xserver version we have
> that support AIGLX is dropped. For now, it is just an package option
> that is only available with some versions (1.17 and 1.14).
As I understood it, AIGLX support is now unconditionally enabled:
https://cgit.freedesktop.org/xorg/xserver/commit/?id=501d8e2beb337e072c93c9310fcd927a099b9c3b
So the legacy option would just state that this option is now
unconditionally enabled. I'm not sure how helpful that is. The user is
presumably already notified that the server version has changed
(E.G. from 1.14/1.17 to 1.19+).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-01-26 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 22:20 [Buildroot] [PATCH] DEVELOPERS: Add entry for upower Romain Naour
2017-01-08 22:20 ` [Buildroot] [PATCH] legacy/xserver: add a legacy entry for xserver >= 1.19.0 Romain Naour
2017-01-24 10:33 ` Thomas Petazzoni
2017-01-25 10:56 ` Arnout Vandecappelle
2017-01-25 19:29 ` Romain Naour
2017-01-26 10:38 ` Arnout Vandecappelle
2017-01-26 20:59 ` Yann E. MORIN
2017-01-26 22:06 ` Peter Korsgaard [this message]
2017-01-09 8:43 ` [Buildroot] [PATCH] DEVELOPERS: Add entry for upower Peter Korsgaard
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=87efzpcw7e.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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