Subject: Package config/var file paths proposal
To: None <firstname.lastname@example.org>
From: Todd Vierling <email@example.com>
Date: 01/06/1999 18:27:10
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
PLEASE GIVE AN OPINION IF YOU FEEL STRONGLY ABOUT ONE OF THESE. This is a
heavily disputed point and needs a concensus.
Note that it can be up to the user to symlink config and volatile files and
directories elsewhere; this indicates only where pkgified programs will
_look for_ their files. This proposal does not say to where $PREFIX points,
but it does assume that $PREFIX follows the same subdirectory hierarchy as
that used for /usr/local, and does not contain a `usr' subdirectory with
bin, sbin, etc. below that.
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
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)
BC ... all pkg-related files may be removed with a `rm -rf' including
binaries and config/volatile files
My personal preference is `A'.
-- Todd Vierling (Personal firstname.lastname@example.org; Bus. email@example.com)