Subject: Re: /usr/pkg/etc vs. /etc
To: What EES eet man? <firstname.lastname@example.org>
From: Manuel Bouyer <email@example.com>
Date: 12/16/1998 10:09:26
On Dec 15, What EES eet man? wrote
> Manuel Bouyer sez:
> * Why ? I don't copy /var/db/pkg, and all my machine run fine. Sure I can't
> * use the pkg_* commands on the rdisted machines, but what's the problem ?
> Well, maybe that's your idea of "fine", and that's fine, but not everyone
> shares the same viewpoint (obviously, from the tack this thread has taken).
> Me, personally, _I'd_ want /var/db/pkg updated because I'd want to know
> which things got installed on which machine. Your kilometrage varies.
In this case I could also rdist /var/db/pkg. But as I only have to look at the
server to know which packages are on my machines ...
> * > I.e. why use the package system in
> * > the first place if you want to avoid doing the "install" step on each
> * > machine?????
> * To have precompiled binaries, or get sources that have already been tested
> * and are known to compile.
> * But I want all my machines to be identical. For this king of setup, rdist is
> * much better suited than any command distribution tool.
> ...in which case you'd probably want to install straight to /usr/local
> and not bother registering the packages.
Registered packages allow me to remove packages from the server. rdist will
remove it from the clients.
> Ideally what you want is not necessarily the package system as it exists,
> but you want a central repository. From what you've stated, the information
> and management provided by the pkg system is completely superfluous.
Not at all, they're still usefull to administrate the server !
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr