Subject: Re: use of share vs lib
To: None <root@garbled.net>
From: Jim Bernard <jbernard@ox.mines.edu>
List: tech-pkg
Date: 07/31/1998 18:42:52
On 7 31, Tim Rightnour wrote:
> It occurred to me again why I disklike /var for HS's and why I also am unsure
> about the idea of putting db files in /usr/pkg/{etc,var}
> 
> Look at a pkg like ssh.  It installs a bunch of binaries, then generates it's
> magical key, and installs config files in /etc.  If these went into
> /usr/pkg/etc, then I would have to devise some sort of wierd symlink tree like
> Todd mentioned, in order to get things right for my multiple machines.  In
> With the pkg dirs in /var, I can run to each machine, install ssh, and get the
> /etc stuff that I need placed there.  With a single db dir shared.. I'm going
> to have alot of trouble doing this.

  You don't need to install ssh to generate the keys--just run ssh-keygen and
copy the config files you want to use, or, if you have the Makefile handy,
make whatever target is provided to set up the local state info (keys, configs,
etc.).

> Not that *either* way is a very clean approach to it.. but putting things in
> /usr/pkg/etc forces someone to create a symlink trick or something (which we
> don't supply) and is slightly less than intuitive.

  Well, the pkg system db files should be shareable, since they specify the
state of the (possibly shared) tree.  But, one could argue that the pkg
system etc files should not, though it may be fairly harmless in many cases.