From owner-freebsd-x11@FreeBSD.ORG Sun Feb 1 13:11:23 2009 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 990CA1065672 for ; Sun, 1 Feb 2009 13:11:23 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 43F4C8FC08 for ; Sun, 1 Feb 2009 13:11:23 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from OMTA10.westchester.pa.mail.comcast.net ([76.96.62.28]) by QMTA10.westchester.pa.mail.comcast.net with comcast id AckT1b0020cZkys5AdBPQp; Sun, 01 Feb 2009 13:11:23 +0000 Received: from daland.home ([24.34.211.11]) by OMTA10.westchester.pa.mail.comcast.net with comcast id AdBP1b0060FJTGg3WdBPTD; Sun, 01 Feb 2009 13:11:23 +0000 Received: from algo by daland.home with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LTc6b-000Oho-Ux; Sun, 01 Feb 2009 08:11:21 -0500 From: Alex Goncharov To: Matt Dawson In-reply-to: <200902011233.57132.matt@chronos.org.uk> (message from Matt Dawson on Sun, 1 Feb 2009 12:33:56 +0000) References: <200901311153.58361.vehemens@verizon.net> <200902011233.57132.matt@chronos.org.uk> Message-Id: Sender: Alex Goncharov Date: Sun, 01 Feb 2009 08:11:21 -0500 Cc: freebsd-x11@freebsd.org, alex-goncharov@comcast.net Subject: Re: Unhappy Xorg upgrade X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Goncharov List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2009 13:11:24 -0000 ,--- You/Matt (Sun, 1 Feb 2009 12:33:56 +0000) ----* | Yes, it can. Read the man page for csup. You can set something like | tag=. date=2008.12.20.12.00.00 in your supfile and get back to (within reason) | any historic point in the tree. That is wonderfully nice -- thank you. | You can also tell portupgrade, if you use it, to hold off on certain | upgrades (try pkg_info -r xorg-7.3_2 for a full list of packages to | hold in portupgrade.conf, HOLD_PKGS define) if you want to stay | current, although I can see a few ports failing with odd deps after | they've been touched by the Xorg bump, so you'd probably be better | off using the supfile's date method to preserve compatibility | between ports. OK, now the idea of how to keep a part of my port system old and the other part new is beginning to shape in my head... A bit of pain but should be doable. | That is not to say the new Xorg doesn't work. The only problems I've | seen on Radeons needed a couple of options lines in xorg.conf due to | the hald/dbus/xorg race and an fdi to make the keyboard layout match | what I actually have rather than "us". Easily fixed for now and 7.4 | brings some fixes to my systems that I have been awaiting for quite | some time, most notably the horrendous XPress 200M chipset now works | with DRI. Knowing about specific things now fixed for specific users is very encouraging. Thanks a lot! -- Alex -- alex-goncharov@comcast.net --