From owner-freebsd-stable@FreeBSD.ORG Wed May 23 22:17:51 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 EADB916A469 for ; Wed, 23 May 2007 22:17:51 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 6AE4613C448 for ; Wed, 23 May 2007 22:17:51 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l4NMHG02025916; Wed, 23 May 2007 19:17:16 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: Roland Smith Date: Wed, 23 May 2007 19:16:14 -0300 User-Agent: KMail/1.9.6 References: <200705211823.29943.ABabiy@shaw.ca> <200705231818.13588.joao@matik.com.br> <20070523214641.GG3705@slackbox.xs4all.nl> In-Reply-To: <20070523214641.GG3705@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200705231916.15624.joao@matik.com.br> X-Spam-Status: No, score=-100.5 required=5.0 tests=ALL_TRUSTED, AWL, MR_DIFF_MID, SMILEY,USER_IN_WHITELIST autolearn=unavailable version=3.1.8 X-Spam-Checker-Version: Antispam Datacenter Matik msrv.matik.com.br X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, Iulian M Subject: Re: xorg 7.2 start problem 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: Wed, 23 May 2007 22:17:52 -0000 On Wednesday 23 May 2007 18:46:41 Roland Smith wrote: > On Wed, May 23, 2007 at 06:18:12PM -0300, JoaoBR wrote: > > On Wednesday 23 May 2007 17:51:34 Roland Smith wrote: > > > On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote: > > > > I also haven't read anything and got terrible caught by this 7.2 xo= rg > > > > thing > > > > > > Says it all, really. :-) > > > > you're not laughing at me aren't you? > > A little. Ignoring /usr/{ports|src}/UPDATING usually has predictable > results. Been there, done that. :-) > good to know, so at the end nobody is alone and some beast will bite me aga= in=20 sooner or later at the same place :) > > > > and kind of lame that portupgrade xorg does not install the modules, > > > > > > And how is portupgrade to know which specific drivers you need? > > > > good question deserve good answers: how the heck portupgrade did it > > before? > > 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= =20 them all as before (when they were in the package) I believe that is unusual that some de-installs xorg and installs the meta= =20 port then and also I am not sure but I believe that xorg needs some drivers= =20 in any case so it should be a necessary step or dependency here > > That's funny. :-) If you can't be bothered to read UPDATING, you are not > the person to tell the maintainers that they haven't "thought it > through". yup, that is right but life is hard either way and it is never fair to all = of=20 us, but then, thinking well, we might discover that the critics are ever a= =20 valid input even if appear to one or another as offense they might not been= =20 thought to be so > > 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= =20 then it would be wise to advise more clearly what is happening from within= =20 the upgrade process because almost nobody reads the files especially when h= e=20 portupgraded flawless something like xorg for years, even from x86 to xorg= =20 was a no-issue at all but there was a scary name-change.=20 other ports do it for less and a message like local base has changed you ne= ed=20 to edit your xorg.conf or something would do good here =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br