From owner-freebsd-stable@FreeBSD.ORG Fri May 25 16:54:11 2007 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED2E716A46C for ; Fri, 25 May 2007 16:54:11 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 5B0F913C43E for ; Fri, 25 May 2007 16:54:10 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (urahsr@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l4PGs4aO093255 for ; Fri, 25 May 2007 18:54:10 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l4PGs4QN093254; Fri, 25 May 2007 18:54:04 +0200 (CEST) (envelope-from olli) Date: Fri, 25 May 2007 18:54:04 +0200 (CEST) Message-Id: <200705251654.l4PGs4QN093254@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200705231916.15624.joao@matik.com.br> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 25 May 2007 18:54:10 +0200 (CEST) Cc: Subject: Re: xorg 7.2 start problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 16:54:12 -0000 JoaoBR wrote: > Roland Smith wrote: > > It didn't. All the drivers were in one huge package, the X server. Now > > they are in seperate ports. But the xorg or xorgs-drivers meta-ports > > should install all of them. > > ok, that is what I ment, the better way would be that portupgrade installs > them all as before (when they were in the package) That's exactly what happens when you install the xorg meta port (as explained in the UPDATING instructions). > > Tools like portupgrade and portmaster and even the ports system are > > great but they have their limitations. I think they are kept relatively > > simple for a reason. It's much better to have a simple (maintainable) > > tool that does 95% of the jobs well than to build an extremely > > complicated ACME contraption that can cover all the corner cases and > > oddball situations. It's just not worth the effort. > > I agree and totally understandable but when there is a big change involved > then it would be wise to advise more clearly what is happening from within > the upgrade process because almost nobody reads the files I think that's wrong. Almost everybody reads UPDATING. Those who don't start threads on one of the mailing lists. > other ports do it for less and a message like local base has changed you need > to edit your xorg.conf or something would do good here If someone refused to read UPDATING, then why would he not ignore a message that scrolls through the screen at some point? As others have already stated, there are very detailed instructions in /usr/port/UPDATING. You should not blindly update your ports without looking at that file. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd With Perl you can manipulate text, interact with programs, talk over networks, drive Web pages, perform arbitrary precision arithmetic, and write programs that look like Snoopy swearing.