Date: Sun, 28 Oct 2001 13:45:06 -0800 From: Eric Melville <eric@FreeBSD.org> To: The Anarcat <anarcat@anarcat.dyndns.org> Cc: "Simon L. Nielsen" <simon@nitro.dk>, binup@FreeBSD.org, libh@FreeBSD.org Subject: Re: current project steps Message-ID: <20011028134506.B15301@FreeBSD.org> In-Reply-To: <20011026165952.D11804@shall.anarcat.dyndns.org>; from anarcat@anarcat.dyndns.org on Fri, Oct 26, 2001 at 04:59:52PM -0400 References: <20011020202153.A76835@FreeBSD.org> <20011026135930.03D1637B406@hub.freebsd.org> <20011026165952.D11804@shall.anarcat.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I think what binup should concentrate on is the client/server paradigm > because the package system is already under way. We've already got that designed, and for the most part, implemented as well. > We probably need pkg-plists. Even if that sucks. 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? > It would probably be possible to create packages from /usr/obj (or > equivalent), and then install these, but the fundamental problem is > that: > > cd /foo/bar ; make install > > is more efficient than > > cd /foo/bar ; make package ; pkg_add bar.tgz Yes, but what I've got in mind is making the install target smart enough to update the package database. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-binup" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011028134506.B15301>