On Monday 04 April 2005 15:31, Arnaud Kyheng wrote: > severity 301822 wishlist > thanks > > Hi all, > > Daniel Baumann wrote: > > I second that, otherwise it should be, for consistency, /var/lib/GNUnetd > > etc. too. > > Mmmmm that's right. > I can't find anything in the Debian policy related to the logfile names. > What about renaming all default directories to /.../GNUnet or /.../gnunet ? > > What do you think about it Christian ?
We're using lib/GNUnet/ and include/GNUnet/ in 0.7.x. So I don't see anything wrong with /var/lib/GNUnet for data. And it is not _only_ gnunetd that accesses that data (gnunet-transport-check, gnunet-update and gnunet-peer-info will also access /var/lib/GNUnet/. So calling it after the binary (gnunetd) is not such a great idea. As for logs, /var/log/GNUnet (file or directory? dunno, depends on general policy) would probably make sense for consistency. However, setting the log path is probably not an issue for upstream (i.e. me) since I think the current definition (relative to GNUNETD_HOME) is a reasonable default for non-distribution setups (as in, /var/log may not always be viable). In the long run I hope to have gnunetd automatically detect if it has access to /var/lib, /var/log, /etc/gnunet.conf and then automagically switch the paths to either the "root"-style installation or the "$HOME"-style installation. But that's still future work. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
