From owner-freebsd-arch Sun Jul 14 16:48:41 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 82AE537B400 for ; Sun, 14 Jul 2002 16:48:38 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3A0A43E4A for ; Sun, 14 Jul 2002 16:48:37 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.12.5/8.12.5) with ESMTP id g6ENla0L039627; Sun, 14 Jul 2002 19:47:36 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200207142347.g6ENla0L039627@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: Thomas Seck , freebsd-arch@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" 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> <3D31F81E.290289FD@mindspring.com> In-reply-to: Your message of "Sun, 14 Jul 2002 15:15:58 PDT." <3D31F81E.290289FD@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Jul 2002 19:47:36 -0400 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 I disagree. I think of two classes of users of the FreeBSD system. They are: A) Those that install releases from a CDROM from time-to-time. 2) Those that follow FreeBSD development on an on-going basis (e.g., bleeding edge -CURRENT or production -STABLE users). The "A" class of users don't need a package management system to maintain their systems as part of the FreeBSD base system. E.g., they use tools like sysinstall which isn't even built by "make buildworld", but is available on the distribution CDROM they booted. The "2" class of users use tools like cvsup which isn't part of the base system to keep their source code/repositories up to date. They manage to do this by using a tool in the ports/packages system. Many of them also choose to use tools like portupgrade, also in ports/packages. So why is it the package management infrastructure is required to be in the base system, when to a large extent it's not today? What's it mean to be part of the "base system" when everything turns into optional components? louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message