From owner-freebsd-arch Sun Jul 14 15:16:59 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 2858037B400 for ; Sun, 14 Jul 2002 15:16:56 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9900643E4A for ; Sun, 14 Jul 2002 15:16:55 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0036.cvx21-bradley.dialup.earthlink.net ([209.179.192.36] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17TrfW-0007Zn-00; Sun, 14 Jul 2002 15:16:43 -0700 Message-ID: <3D31F81E.290289FD@mindspring.com> Date: Sun, 14 Jul 2002 15:15:58 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Thomas Seck , freebsd-arch@FreeBSD.ORG Subject: Re: Package system flaws? References: <20020712121427.GD3678@lummux.tchpc.tcd.ie> <20020712144854.GA756@laurel.tmseck.homedns.org> <20020713054141.A26277@misty.eyesbeyond.com> <20020713011750.GA755@laurel.tmseck.homedns.org> <20020714042237.GD931@lizzy.catnook.com> <20020714042623.GB95460@squall.waterspout.com> <20020714095939.GA588@laurel.tmseck.homedns.org> <200207141333.g6EDXj0L031673@whizzo.transsys.com> <20020714155728.GA4237@laurel.tmseck.homedns.org> <200207141624.g6EGOa0L033175@whizzo.transsys.com> 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 "Louis A. Mamakos" wrote: > And so what's so difficult to understand? Why is it that the only > tools "qualified" for use in maintaining the ports on a machine seem > to be required to be in the base system? From what I can tell, the > direction is to move non-essential stuff out of the base system. Because *in order to* move stuff out of the base system as transparently as possible, the base system itself needs to be under the purview of the package management system. In other words, the difference between a "PicoBSD" and a standard minimal installation and a full installation should come down to two things: 1) What shows up when you list installed components 2) What configuration data is mandatory > Again, I don't see why it's so burdensome to type 'make install' in > the /usr/ports/sysutils/portupgrade directory. It doesn't solve some problems that people would like to see solved for them. 8-). [ ... ] > Why do you care what the implementation language of the tool is if it > solves the problem? Shouldn't we be pleased there even exists a tool > in the first place? The implementation language of any tool is irrelevent, so long as the tool works, and so long as it can be maintained if the person who wrote/maintains it get hits on the head by a falling Sputnik. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message