From owner-freebsd-binup Sun Oct 28 15:59:11 2001 Delivered-To: freebsd-binup@freebsd.org Received: from tomts12-srv.bellnexxia.net (tomts12.bellnexxia.net [209.226.175.56]) by hub.freebsd.org (Postfix) with ESMTP id 40FF237B405; Sun, 28 Oct 2001 15:59:03 -0800 (PST) Received: from khan.anarcat.dyndns.org ([65.94.136.15]) by tomts12-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011028235901.WVKY10438.tomts12-srv.bellnexxia.net@khan.anarcat.dyndns.org>; Sun, 28 Oct 2001 18:59:01 -0500 Received: from shall.anarcat.dyndns.org (shall.anarcat.dyndns.org [192.168.0.1]) by khan.anarcat.dyndns.org (Postfix) with ESMTP id B3D2319FB; Sun, 28 Oct 2001 18:58:58 -0500 (EST) Received: by shall.anarcat.dyndns.org (Postfix, from userid 1000) id 35A4E20ACE; Sun, 28 Oct 2001 18:59:46 -0500 (EST) Date: Sun, 28 Oct 2001 18:59:45 -0500 From: The Anarcat To: Paul Richards Cc: Alexander Langer , Josef Karthauser , "Simon L. Nielsen" , Eric Melville , binup@FreeBSD.org, libh@FreeBSD.org Subject: Re: current project steps Message-ID: <20011028185945.E71544@shall.anarcat.dyndns.org> References: <20011026165952.D11804@shall.anarcat.dyndns.org> <20011026221254.A36515@tao.org.uk> <20011026172027.F11804@shall.anarcat.dyndns.org> <20011026223033.A44573@tao.org.uk> <20011027131726.A68253@shall.anarcat.dyndns.org> <20011027210157.D1534@tao.org.uk> <20011028100459.A40262@fump.kawo2.rwth-aachen.de> <361480000.1004271794@lobster.originative.co.uk> <20011028132639.A71003@shall.anarcat.dyndns.org> <11770000.1004307790@lobster.originative.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ryJZkp9/svQ58syV" Content-Disposition: inline In-Reply-To: <11770000.1004307790@lobster.originative.co.uk> User-Agent: Mutt/1.3.22.1i 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 --ryJZkp9/svQ58syV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun Oct 28, 2001 at 10:23:10PM -0000, Paul Richards wrote: > --On Sunday, October 28, 2001 13:26:40 -0500 The Anarcat > wrote: >=20 > > On Sun Oct 28, 2001 at 12:23:14PM -0000, Paul Richards wrote: [btw, is it me or is this 2 hours *after* your last reply?] > >> If libh is an installation tool then it shouldn't be concerned with > >> package formats. > >=20 > > That is the main failed predicate. Libh is not *just* an installation > > tool. Trivial installation tools are written within libh because it's > > the only place they can be developped, but they are only consumers, and > > not part of the library. > >=20 > > Some part of the library can be used in installation programs, but that > > is all. > >=20 > > Libh is concerned with package formats because FreeBSD package format > > needed a rewrite. That is done.=20 >=20 > My impression though is that this new package format is totally dependent > upon the architecture of libh, in that the packages themselves are expect= ed > to carry large amounts of intelligence in the form of embedded tcl. All > that libh really does is provide a framework for packages to execute their > embedded tcl that describes how they should be installed. Actually, it's the other way around. Libh architecture is based on the package format. :) But I now understand more clearly the concerns. Indeed, the package format is arguable. > That's nothing like the design Joe and I have been thinking about. I didn't know this design included package formats. > The approach I want to take is to come up with a specification for the A= PI > that can then be implemented independently by different coding teams (if > there's interest). At the moment, all we have are one-off implementations, > no-one has ever written a specification that others can follow if they wi= sh > to write their own conforming installation tools. I don't feel that design is in "contradiction" with libh's. You only mention having an API *over* libh and any other package format. Am I wrong? Couldn't libh package system be used within this new API? Or libh API changed to fit this new API? I guess I'm getting confused over your concerns here... > One group may want to write a perl intaller, libh would use tcl, another > group might use C etc. The task that needs to be completed successfully > with some foresight and planning is the specification of the API, sitting > down and designing the API before any code is written will result in a mu= ch > more complete an well thought out design. Agreed. However, it is too late. Code has already been written. Heck, even the old package tools count in there. :) A. --ryJZkp9/svQ58syV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvcm+8ACgkQttcWHAnWiGfWTwCgpQT8793DBdtkOzAuXGPHCw8x 8jQAoJ4WFrgSccJSx0S3H1vh6DQWiGJB =+pul -----END PGP SIGNATURE----- --ryJZkp9/svQ58syV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-binup" in the body of the message