From owner-freebsd-stable@FreeBSD.ORG Mon Jul 7 09:58:38 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 855AFEA3 for ; Mon, 7 Jul 2014 09:58:38 +0000 (UTC) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow Root Certificate 2010-04-12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE077220F for ; Mon, 7 Jul 2014 09:58:37 +0000 (UTC) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801::46]) by mta1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s679wWdS005942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 7 Jul 2014 19:58:32 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1404727112; bh=015DLUxBvxF3mqnsgbIvrmCgRli732G7GVtwqjxqFM8=; h=Date:From:To:Subject:References:In-Reply-To; b=qy9omcqUDge5i4XkEn4NVP+yqRcAHNRWzxtzjAuy182+Zw4qM/4haBj94SyCADOdd /c2yHZfq2OLNWCEgIJVRCTO7Qsqp6TWxumN/cUUWiFkdy4PyQLx68c/Zn75L1F/5rn k0COEEOjDpg9pTcuriAq+P6s36MLdR7qt+eOEGfA= Received: from rwpc15.gfn.riverwillow.net.au (rwpc15.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:20c:76ff:fe0a:2117]) (authenticated bits=56) by mail1.riverwillow.net.au (8.14.9/8.14.9) with ESMTP id s679wQLo005941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 7 Jul 2014 19:58:27 +1000 (AEST) Date: Mon, 7 Jul 2014 19:58:26 +1000 From: John Marshall To: freebsd-stable@freebsd.org Subject: Re: Should 9.3 carry a warning about NEW_XORG Message-ID: <20140707095825.GB1074@rwpc15.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@freebsd.org References: <53B69B88.4060803@gmail.com> <20140705103235.GB7680@rwpc15.gfn.riverwillow.net.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LyciRD1jyfeSSjG0" Content-Disposition: inline In-Reply-To: OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 09:58:38 -0000 --LyciRD1jyfeSSjG0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. > 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. --=20 John Marshall --LyciRD1jyfeSSjG0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlO6b0EACgkQw/tAaKKahKIX3QCghPAgvjHe7f1JGytBR8csFVsp xjcAoMeWmnNxmf41jxrztlXOeR0gSG+z =iXWy -----END PGP SIGNATURE----- --LyciRD1jyfeSSjG0--