From owner-freebsd-chat@FreeBSD.ORG Mon Aug 4 14:26:31 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3320937B401; Mon, 4 Aug 2003 14:26:31 -0700 (PDT) Received: from praetor.linc-it.com (hardtime.linuxman.net [66.147.26.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58C3C43F75; Mon, 4 Aug 2003 14:26:30 -0700 (PDT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-19-129-168.jan.bellsouth.net [68.19.129.168]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by praetor.linc-it.com (Postfix) with ESMTP id 39B85152A5; Mon, 4 Aug 2003 16:26:29 -0500 (CDT) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 22DC420F26; Mon, 4 Aug 2003 16:26:26 -0500 (CDT) Date: Mon, 4 Aug 2003 16:26:26 -0500 From: "Matthew D. Fuller" To: Scott Long Message-ID: <20030804212626.GM1161@over-yonder.net> References: <1059994012.207.5.camel@localhost> <20030804174619.GD68433@roark.gnf.org> <20030804184827.GD56633@survey.codeburst.net> <20030804.131957.05878097.imp@bsdimp.com> <20030804203846.GA97580@dragon.nuxi.com> <20030804204806.GA59103@rot13.obsecurity.org> <3F2ECBC9.7020808@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F2ECBC9.7020808@freebsd.org> User-Agent: Mutt/1.4.1i-fullermd.1 X-Editor: vi X-OS: FreeBSD cc: chat@freebsd.org cc: David O'Brien cc: Kris Kennaway Subject: Re: pkg_* tools X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 21:26:31 -0000 On Mon, Aug 04, 2003 at 03:10:33PM -0600 I heard the voice of Scott Long, and lo! it spake thus: > Kris Kennaway wrote: > > > >Please explain. I think this is FUD - nothing has come to depend on > >portupgrade, except that it provides useful features that the ports > >collection itself never has. Trying to keep things updated and in sync, while technically possible without portupgrade, rapidly approaches the joy factor of slivers of magnesium inserted under your fingernails and ignited. While having your eyes inspected by masonry drills. > The 'fontconfig' mess of recent XFree86 has made a royal mess of things, > and the common response I hear to that is, "the ports system is > fundamentally flawed and cannot be taught to deal with it, but > portupgrade can". However, the times that I've tried to install > portupgrade on a non-virgin system (i.e. a system that has been around > for a few months and has had many ports installed through the > traditional means), it winds up horribly screwing my installation and > leaving many things, most notably X, damaged and unusable. I've heard > the same horror stories from others around me. It should be noted that I took the plunge sometime (earlier this year, or late last) and installed portupgrade to mess with it. I installed this system in early 1999 with an early 4.0-CURRENT, and installed, upgraded, deinstalled, didn't-deinstall-but-did-whack-the-pkg-dir, partially-deinstalled, installed-over, installed 3 and 4 versions, partially overlapping files, and did all sorts of unspeakable things to it for years. I managed to trend things toward a bit cleaner layout with portupgrade. Now, I never give it its head. I rarely use the recursive features, instead sifting through portversion and giving it a long list manually, which it then internally sorts into the 'optimal' order. It's rather messy in places, to be sure, but after years of managing ports manually... yeah, it's an improvement. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet"