Date: Mon, 7 Jul 2014 09:39:06 -0700 From: Adrian Chadd <adrian@freebsd.org> To: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: Should 9.3 carry a warning about NEW_XORG Message-ID: <CAJ-VmokU0H2mQi-6DMnJH07GpkrXt4mEeNLcFDeKF90bTFHFGg@mail.gmail.com> In-Reply-To: <20140707095825.GB1074@rwpc15.gfn.riverwillow.net.au> References: <53B69B88.4060803@gmail.com> <E1X32XF-000PnU-QG@dilbert.ingresso.co.uk> <CAPyFy2BhARs%2BwxhOuP-09tcPgzerU00_ARy=o4OyKec9azTOkQ@mail.gmail.com> <20140705103235.GB7680@rwpc15.gfn.riverwillow.net.au> <CAJ-VmomJByjDRrua2r6qevJ%2B_M8R5joHZ5gUP=OYh1KszZt6wQ@mail.gmail.com> <20140707095825.GB1074@rwpc15.gfn.riverwillow.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 July 2014 02:58, John Marshall <john.marshall@riverwillow.com.au> wrote: > On Sat, 05 Jul 2014, 11:46 -0700, Adrian Chadd wrote: >> The TL;DR reason for going up to building with new-xorg is because >> without it, an increasing number of X related ports plainly won't >> build anymore. They assume the newer X and DRI libraries. > > Thank you for this explanation: it helps. > >> So the choice is (a) new_xorg and pain, (b) no new_xorg and a lot of X >> packages not getting upgraded any further, (c) more work on the ports >> maintainers to try and figure out ways to work around an increasingly >> impossible situation. There's also (d) - don't bother with 9.3. > > and (e) add WITHOUT_NEW_XORG to make.conf and upgrade to 9.3; > understanding that this really is the end of the road for X on older > hardware. 9.2 is EOL in a couple of months, so upgrading to 9.3 without > breaking X makes sense to me. Right - but once that knob goes away (because there's only new-xorg) then they'll start updating packages to the latest upstream releases and they may not even compile on your pre-new-Xorg. That will pull in versions of the DRI libraries that won't work. So it's not just going to break your Xorg compilation - it's just plainly not going to work. >> The X ports team has a fast moving target to keep track of and we're >> still not anywhere near the bleeding edge of Linux graphics rendering >> support and all the graphics stuff that moves with it. As much as I >> hate to see lots of churn, it's a losing battle. > > Again, thanks for explaining the X-related development/upgrade dilemma. > The reason for my OP was that bad things happened, unexpectedly, with NO > warning or explanation. Oh, absolutely. I think some of us are just .. not good at communicating technology changes. :) I kinda wished that the Xorg development wouldn't break older graphics rendering so hard, but alas, what drives that is the hardware innovation cycle and not the "holy shit you mean we need to use this for 10 years?" cycle. -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokU0H2mQi-6DMnJH07GpkrXt4mEeNLcFDeKF90bTFHFGg>