Subject: Re: Package config/var file paths proposal
To: None <email@example.com>
From: Simon Burge <firstname.lastname@example.org>
Date: 01/07/1999 14:24:32
On Wed, 6 Jan 1999 18:27:10 -0500 (EST) Todd Vierling wrote:
> In order to make sure these points get implemented, this particular point of
> the `package paths proposal' has been parted out.
> This proposal offers three options wrt handling config file and volatile
> files in pkg distributed programs.
> A: config files go in /etc, volatile files in /var
> B: config files go in $PREFIX/etc, volatile files in $PREFIX/var
> C: config files go in /etc/pkg, volatile files in /var/pkg
> [ ... ]
> this indicates only where pkgified programs will
> _look for_ their files.
> [ ... ]
> Below lists various points of the options above, and a latter A, B, or C
> by each points indicates which one of the above satisfies the given point.
> B ... files are NFS shared by default if $PREFIX is shared
Bad - but then ssh and others already work around this.
> A C ... files are not NFS shared by default if $PREFIX is shared
> A ... files are mixed in with system configuration files without
> distinguishing between system and pkg programs (typically the
> same place as for an `out of the box' install)
With a file-to-package database, not too much of a problem. Especially
less so if we move to a base system that is also based on packages one
> BC ... all pkg-related files may be removed with a `rm -rf' including
> binaries and config/volatile files
> My personal preference is `A'.