Date: Thu, 29 Jan 2009 09:25:28 -0500 From: Alex Goncharov <alex-goncharov@comcast.net> To: Robert Noland <rnoland@FreeBSD.org> Cc: freebsd-stable@freebsd.org, danallen46@airwired.net, bms@FreeBSD.org, freebsd-ports@freebsd.org, alex-goncharov@comcast.net Subject: Re: Unhappy Xorg upgrade Message-ID: <E1LSXpg-000ARc-C2@daland.home> In-Reply-To: <1233238367.1779.47.camel@wombat.2hip.net> (message from Robert Noland on Thu, 29 Jan 2009 09:12:47 -0500) References: <6B7ABE80-35AB-4C44-B5A4-200E10DCC3AC@airwired.net> <E1LSP0B-0003Ds-H8@daland.home> <49819BD5.5040709@FreeBSD.org> <E1LSWHr-0009TS-P7@daland.home> <1233236412.1779.40.camel@wombat.2hip.net> <E1LSXPn-000ABB-4L@daland.home> <1233238367.1779.47.camel@wombat.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
,--- You/Robert (Thu, 29 Jan 2009 09:12:47 -0500) ----* | Problem is, it isn't just the Xserver... All of the pieces are | intertwined and so in many cases to update Xserver you also need to | update some/several libraries as well as all of your drivers. Xorg is | about 60 or 70 ports now. That can be handled, it seems to me. My current port upgrade problem is that I cannot csup the tree and get the old X to rebuild dependent components. | FWIW, I have Xserver 1.6 and xrandr bits that are rc already... as well | as a new intel driver that I don't want to update without xserver 1.6. I would be willing to test 1.6 on my many different machines, provided there is a clear and inexpensive (< 2 hours) path to a rollback. -- Alex -- alex-goncharov@comcast.net --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1LSXpg-000ARc-C2>