From owner-freebsd-arch Fri Sep 6 5:17:28 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9631C37B400; Fri, 6 Sep 2002 05:17:23 -0700 (PDT) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2958443E75; Fri, 6 Sep 2002 05:17:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0015.cvx21-bradley.dialup.earthlink.net ([209.179.192.15] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17nI2Y-0005OL-00; Fri, 06 Sep 2002 05:16:46 -0700 Message-ID: <3D789C68.4B82930@mindspring.com> Date: Fri, 06 Sep 2002 05:15:36 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Simon 'corecode' Schubert Cc: Wes Peters , will@csociety.org, dwcjr@inethouston.net, ports@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: package tools into ports/ References: <20020901142653.A32415@capable.rogards.com> <20020901191937.GI87971@leviathan.inethouston.net> <20020902103215.36ae8e3b.corecode@corecode.ath.cx> <20020902085654.GH2072@procyon.firepipe.net> <3D7445D3.DAA2C9B9@softweyr.com> <20020906133436.32554344.corecode@corecode.ath.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Simon 'corecode' Schubert wrote: > On Mon, 02 Sep 2002 23:17:07 -0600 Wes Peters wrote: > > OK, how do you install the package tools package onto the system if it > > doesn't come with package tools? > > how about always building the package tools if they are outdated? or > providing a special package for them plus a small script which will > install that package... I believe the intent is to allow replacement of the existing installed package tools with a new set of package tools which are mostly the same, but include Bzip support. I have no idea why anyone wants bzip support, but this seems to be the driver for this issue. So for Wes: They don't want to take the package tools out of the base system, they just want to be able to replace them with a version which is compiled seperately to add features (because of a GPL'ed library? I dunno...). For everyone else: it wasn't clear reading through the first couple of messages that you in fact were going to leave the default package tools in place, and replace the installed binaries with new ones. Given the way bzip archives are handled, such that you can't read the index until you have the whole file, I personally do not see the reason for bzip. OPver network links, it will mean taking a long time to download something only to find out you need to download prerequisites. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message