From owner-freebsd-stable@FreeBSD.ORG Sat Jan 31 20:50:12 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B5E11065677; Sat, 31 Jan 2009 20:50:12 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from vms173007pub.verizon.net (vms173007pub.verizon.net [206.46.173.7]) by mx1.freebsd.org (Postfix) with ESMTP id F0EF98FC17; Sat, 31 Jan 2009 20:50:11 +0000 (UTC) (envelope-from vehemens@verizon.net) Received: from sam ([71.107.27.218]) by vms173007.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-2.01 (built Jun 13 2007; 32bit)) with ESMTPA id <0KEC001ZUPON8R36@vms173007.mailsrvcs.net>; Sat, 31 Jan 2009 13:48:24 -0600 (CST) From: vehemens To: freebsd-x11@freebsd.org, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Date: Sat, 31 Jan 2009 11:53:58 -0800 User-Agent: KMail/1.9.10 MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline Message-id: <200901311153.58361.vehemens@verizon.net> Cc: Subject: Re: Unhappy Xorg upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Jan 2009 20:50:12 -0000 On Fri Jan 30 11:53:16 PST 2009, Peter Jeremy wrote: >As a general note, this is the second time in a row that an X.org >upgrade broke X for a significant number of people. IMO, this >suggests that our approach to X.org upgrades needs significant changes >(see below). X11 is a critical component for anyone who is using >FreeBSD as a desktop and having upgrades fail or come with significant >POLA violations and regressions for significant numbers of people is >not acceptable. The problem isn't so much as a problem with xorg updates as it is with the overall port approach. Not having a stable versus current ports approach is probably the biggest cause of the problems seen here. The port freezes don't help either. In general when upgrading, you take your chances. If a port upgrade fails, you should fall back to what worked. Trying to partial rebuild ports versus rebuilding from scratch after a major update is just asking for problems. There probably needs to be a more incremental approach when upgrading major ports. For example, I updated my system a piece at a time over the last several months, and had no significant problems with the offical x11 upgrade as the changes were small. And last, many of the video drivers have little if any support. If you have something other then ati/intel/nivdia, you should expect problems. Input drivers are in a similar state.