,--- You/James (Sat, 31 Jan 2009 19:50:15 -0500) ----* | Alex Goncharov wrote: | | > That's useful -- I didn't know about ports-mgmt/portdowngrade. Thank | > you! | | It's not that useful because very few ports mirrors allow anon-cvs | access, mostly just cvsup/csup. The last time I had to use it, I | found a mirror in Germany that worked, after a long search.
Thanks for this info, too -- now I'll be prepared to at least some failures on my way. | The Xorg update was a minor disaster, and it's nobody's fault. Fault or not fault, but it seems to me that this upgrade should have been actively warned about and discussed at least two weeks before it happened. In one of my earlier messages, I mentioned that when I had tried to bring X on my laptop to life, I did plenty of Web searching and reading. The number of problems with xorg-server 1.5 reported by Linux users stunned me -- I remember one Debian user had to get the old X from a different release of Debian in order to make his system operational. What was expected to happen on FreeBSD with this X? A smooth fly for everybody -- or some "acceptable" number of hardware configurations allowing the use of the new X? | More testing was needed on lots more systems Yes. | and that can only really happen after committal. No -- a patch might (*should*, for this kind of a disruptive change) be put together: I'd install it on my systems, I'd try it and report problems, I'd revert back -- easily. This is for many "I"s willing to be the testers -- we'd repeat this again as many times as necessary, before the commit. -- Alex -- alex-goncha...@comcast.net -- _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
