Henry Baragar said:
> $PREFIX/bin - the 2 executables + misc scripts
> $PREFIX/man - the man pages
This should only happen if --prefix={} and --datadir={} are identical.
Otherwise, man pages go in $DATADIR/man (that is, unless a --mandir
override is given), where $DATADIR is generally $PREFIX/share.
> $PREFIX/logs - the logs
> I think I prefer $PREFIX/log (ala DJB).
In both cases, I disagree. Either should only happen if you deliberately
set --logdir to something outside of $LOCALSTATEDIR, otherwise they should
go in $LOCALSTATEDIR/log (typically $PREFIX/var). Again, this is unless a
--docdir override is given.
> $PREFIX/etc ?? - config file
Yes. Some packages are doing $PREFIX/etc/$PACKAGE instead, but I really
don't think that should happen unless I override --sysconfdir.
> Do you really want the logs under the same dir as the executables?
This is what $PREFIX is for. If I'm setting up a new linux system on a
new partition mounted at /mnt/newlinux, and I compile bincimap with
PREFIX=/mnt/newlinux, I don't want bincimap putting files on my host
system _at all_.
It's really quite literal in meaning. $PREFIX, the directory _prefix_.
The bit that's supposed to be prefixed onto every directory path unless
specifically overridden.
This is well-documented in coding standards, nearly any existing
application, and probably autoconf documentation too.
--
Casey Allen Shobe
Open Source Software Solutions
[EMAIL PROTECTED]