Date: Thu, 07 Jun 2012 23:12:13 +0200 From: Mel Flynn <rflynn@acsalaska.net> To: freebsd-x11@freebsd.org Subject: Re: [CFT] Xorg 7.7 ready for testing! Message-ID: <4FD1192D.5080404@acsalaska.net> In-Reply-To: <1339102434021-5716310.post@n5.nabble.com> References: <20120607203753.2466c63a.miwi@FreeBSD.org> <alpine.BSF.2.00.1206070801250.53425@wonkity.com> <1339084799874-5716221.post@n5.nabble.com> <4FD0E6B3.2070409@acsalaska.net> <1339102434021-5716310.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7-6-2012 22:53, Jakub Lach wrote: > You are obviously right, I was not referring (or thinking) of > version variables subgroup (like perl which I mentioned) but > that most of them can be set like =true, =yes, =whatever > > It's rather bikeshed. Partly. Tying it to a version is preferable, as you're soon going to run out of _NEWER/_NEWEST variants. You can now make WITH_NEW_XORG an alias for WITH_XORG_VERSION=75 and warn about it being removed real soon now(tm). The other thing is that with all the different modules and their own versioning scheme it's hard to tell what "Xorg version X.Y" really is. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD1192D.5080404>