From owner-freebsd-libh Sun Oct 28 14: 1:45 2001 Delivered-To: freebsd-libh@freebsd.org Received: from tomts14-srv.bellnexxia.net (tomts14.bellnexxia.net [209.226.175.35]) by hub.freebsd.org (Postfix) with ESMTP id AE7B837B403; Sun, 28 Oct 2001 14:01:38 -0800 (PST) Received: from khan.anarcat.dyndns.org ([65.94.136.15]) by tomts14-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20011028220132.GEKM5606.tomts14-srv.bellnexxia.net@khan.anarcat.dyndns.org>; Sun, 28 Oct 2001 17:01:32 -0500 Received: from shall.anarcat.dyndns.org (shall.anarcat.dyndns.org [192.168.0.1]) by khan.anarcat.dyndns.org (Postfix) with ESMTP id 26CEC1A2C; Sun, 28 Oct 2001 17:01:29 -0500 (EST) Received: by shall.anarcat.dyndns.org (Postfix, from userid 1000) id 4F6B520ACE; Sun, 28 Oct 2001 17:02:24 -0500 (EST) Date: Sun, 28 Oct 2001 17:02:24 -0500 From: The Anarcat To: Eric Melville Cc: "Simon L. Nielsen" , binup@FreeBSD.org, libh@FreeBSD.org Subject: Re: current project steps Message-ID: <20011028170223.D71544@shall.anarcat.dyndns.org> References: <20011020202153.A76835@FreeBSD.org> <20011026135930.03D1637B406@hub.freebsd.org> <20011026165952.D11804@shall.anarcat.dyndns.org> <20011028134506.B15301@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cHMo6Wbp1wrKhbfi" Content-Disposition: inline In-Reply-To: <20011028134506.B15301@FreeBSD.org> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --cHMo6Wbp1wrKhbfi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun Oct 28, 2001 at 01:45:06PM -0800, Eric Melville wrote: > > I think what binup should concentrate on is the client/server paradigm > > because the package system is already under way. >=20 > We've already got that designed, and for the most part, implemented as > well. yes, I read a bit about this... Really interesting stuff. > > We probably need pkg-plists. Even if that sucks. >=20 > We're thinking it would be highly useful to have an entirely layer of > abstraction here. Think of a cluster of FreeBSD machines sitting in a lab. > Why not put all their package information into a local Postgres server? Of course. It was the "concept" of the plist I wanted to take note here. Wether it is stored in a SQL database, a file or a piece of paper (not likely :), my point is that we must start recording what gets installed and where, and md5, and etc... > > It would probably be possible to create packages from /usr/obj (or > > equivalent), and then install these, but the fundamental problem is > > that: > >=20 > > cd /foo/bar ; make install > >=20 > > is more efficient than > >=20 > > cd /foo/bar ; make package ; pkg_add bar.tgz >=20 > Yes, but what I've got in mind is making the install target smart enough > to update the package database. Yes, that would be the proper solution. a. --cHMo6Wbp1wrKhbfi 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 iEYEARECAAYFAjvcgG8ACgkQttcWHAnWiGdX3QCgoE5YvnmZXz0jc59VCzkefJiy vbwAoIADeUeiW2gIBweuvTdA0r067a+c =B1zY -----END PGP SIGNATURE----- --cHMo6Wbp1wrKhbfi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message