On Oct 26, 2007 at 12:34 AM, Tomasz Sterna wrote: > Dnia 25-10-2007, Cz o godzinie 17:20 -0700, Mark Doliner pisze: > > > ./configure --prefix=somedir HAVE to move the whole installation to > > > 'somedir'. > > > So we simply cannot use fixed paths. They HAVE to incorporate > $(prefix). > > > > For binaries and documentation I totally agree, but does it make sense > to do that for files created at run time? > > Two examples, that should give some light to the case: > ./configure --prefix=$HOME/test/jabberd > ./configure --prefix=/opt/oss/jabberd > > User definitely cannot keep any data outside $HOME.
True, but in that case they could always edit the config files after building. I think it makes more sense for the default value to be appropriate for a system-wide installation rather than for a user's home directory. > And all data of /opt applications should be kept under /opt hierarchy. I don't think files that change should be put in /opt. The FHS describes a /var/opt directory and says, "Package files that are variable (change in normal operation) must be installed in /var/opt." > > Isn't that MORE of a reason to put the pid files in /var/run? > > It's the decision to be taken during build. > For example, if you're packaging for standard GNU/Linux distribution, > yes it's very reasonable to put pid files in /var/run or /var/run/jabber And that isn't currently possible. Even with a prefix of "/" the pidfile is set to /var/jabberd/pid/component.pid > > If /usr is read-only and jabberd tries to write a pid file to > /usr/var/run it would fail. > > That's why it keeps its state data in @localstatedir@ by default, not > in /usr. But if the prefix is "/usr" then @localstatedir@ is set to "/usr/var" (seems like autoconf and the FHS don't quite agree with each other) -Mark _______________________________________________ Jabberd2 mailing list [email protected] http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
