From owner-freebsd-binup Sun Oct 28 11:43:10 2001 Delivered-To: freebsd-binup@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 3959537B403; Sun, 28 Oct 2001 11:43:07 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f9SJgkf02318; Sun, 28 Oct 2001 11:42:47 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Paul Richards Cc: Alexander Langer , Josef Karthauser , The Anarcat , "Simon L. Nielsen" , Eric Melville , binup@FreeBSD.ORG, libh@FreeBSD.ORG Subject: Re: current project steps In-Reply-To: Message from Paul Richards of "Sun, 28 Oct 2001 12:23:14 GMT." <361480000.1004271794@lobster.originative.co.uk> Date: Sun, 28 Oct 2001 11:42:46 -0800 Message-ID: <2314.1004298166@winston.freebsd.org> From: Jordan Hubbard Sender: owner-freebsd-binup@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If libh is an installation tool then it shouldn't be concerned with package > formats. Ah, here's at least a fundamental misconception we can perhaps address. libh is far more than an installation tool, it's also a replacement for the package tools - that's why it's called "libh" and not simply sysinstalljr or something. A proper installation tool, aided by reasonably intelligent packages which also know how to configure themselves, depends heavily on the model of having the packages do most of the work, the installation tool being little more than bootstrapping code and a specialized execution environment for the package extraction mechanism. Those who are thinking of libh as a single program or mechanism just haven't looked at it deeply enough or read its design specs. It's a collection of tools aimed at solving a much greater set of problems. Than just installation or packaging. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-binup" in the body of the message