Sylvain Beucler <[EMAIL PROTECTED]> tapota : > One idea I have been considering would be to make Savane work like (or using) > autoconf, that would subsitute $SYSCONFDIR in the source files. It would > require a complete installation for each configuration of Savane, though. > > The frontend can already be configured in httpd.conf: > SetEnv SV_LOCAL_INC_PREFIX /etc/myconf
Right, The only issue is to make the backend aware of the content of SV_LOCAL_INC_PREFIX. The easiest solution would be to modify the content of Savannah::Conf during post-installation. But it would implies concurent installation of Savannah.pm -- not clean, maybe even not feasible. I guess we have to find a way to make this runtime configurable. It could be done by passing SV_LOCAL_INC_PREFIX as unix environment setting. An "export SV_LOCAL_INC_PREFIX=prefix" would be added in the generated at install cronfile (/etc/cron.d/savannah). Somehow, it would make sense. And to run the appropriate backend script, admins would have to set SV_LOCAL_INC_PREFIX if non-standard in their terms. Moreover, the frontend should behave the same: setting SV_LOCAL_INC_PREFIX when SV_LOCAL_INC_PREFIX=/etc/savannah should not be mandatory (it is the case currently). Finally, Savane installation process should write an apache.inc file, with correct settings, so users do not have to write it in most of the cases. Now most distros have apache include dirs like /etc/apache/conf.d. This conffile creation should be handled by savane own scripts (sv_update_conf), called by distros tools (so it would be helpful even when doing Debian packaging). That said, it looks like important changes that are worth branching. If you feel ready for that, please go ahead (following the docs), and do not hesitate to get back to the list in case of issue or when you feel it is ready for a merge (ideally it should happen soon ; to old branches are not easy to merge back). Also do not forget to write meaningful log messages -- or better, in docs/devel, a ChangeLog of the branch, ready to be included in the main ChangeLog.byversion once the merge is done. Note that during september I'm hired by the CERN in Geneva to work on Savane. So during this period, I expect a lot of code to be changed/produced on another specific branch (depending on CERN needs). I do not think I'll work on install stuff, so there should not be any CVS conflicts. Several persons said they'll work on Debian packaging. However if nothing is done after september, I'll probably work on it myself, reusing as much as possible work done for Gentoo. Regards, -- Mathieu Roy +---------------------------------------------------------------------+ | General Homepage: http://yeupou.coleumes.org/ | | Computing Homepage: http://alberich.coleumes.org/ | | Not a native english speaker: | | http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english | +---------------------------------------------------------------------+
