On Thu, 2004-03-18 at 02:13, Andreas Aardal Hanssen wrote: > On Thu, 18 Mar 2004, Jeremy Kitchen wrote: > > 1.2.6 final: > > ./configure --prefix=/var/bincimap > > [snip] > > checking --prefix... using /var/bincimap > > checking --sysconfdir... using /var/bincimap/etc > > checking --localstatedir... using /var/bincimap/var > > checking --datadir... using /var/bincimap/share > > These are mistakes in 1.2.6 - it shouldn't be this way.
but I like it! :(
So do I. I certainly don't want all these silly $PREFIX/{etc,var}/opt directories popping up all over the place. All installation paths should be relative to PREFIX unless overridden. This is both what one expects and consistant with the majority of other packages out there. Breaching $PREFIX by default is really quite a bad thing, as one of the reasonings for using it is to contain the entire application within a single directory (consider, --prefix=/opt/bincimap).
If I simply type in --prefix=/usr, then sysconfdir should be /usr/etc, localstatedir should be /usr/var, and datadir should be /usr/share. Based on the given examples, 1.2.6 seems to work like this, just as it should.
Of course, I type in the following after every configure command I can, so this doesn't affect me personally too much. I should have all the bases covered. I don't specify docdir, because it's not supported by many packages, and hopefully when it is it will at least have the sensibility to land in $DATADIR/doc by default:
--prefix= --exec-prefix= --bindir=/bin --sbindir=/bin --libdir=/lib --libexecdir=/bin --datadir=/share --localstatedir=/var --includedir=/include --oldincludedir=/include --infodir=/share/info --mandir=/share/man --sysconfdir=/etc
I guess I'll just have to add more options to configure to put the stuff all in /var/bincimap how I want it :)
I strongly believe that --prefix=/var/bincimap should be enough unless you didn't like the arrangement of the files in the subdirectories thereof.
-- Casey Allen Shobe [EMAIL PROTECTED]
