On Tue, Sep 24, 2013 at 3:51 PM, Galen Charlton <gmc@esilibrary.com> wrote:
Hi,
On Tue, Sep 24, 2013 at 12:54 AM, Mathieu Saby < mathieu.saby@univ-rennes2.fr> wrote:
** Well, so, if I understand, the best would be to write a patch to add "configdir" to koha-conf.xml. Its value should be __KOHA_CONF_DIR__ I suppose? So it could be used by my patch and probably by others.
Actually, I think a path to point to the specific configuration file you're adding is better. The problem with adding a configdir element to koha-conf.xml is that it doesn't distinguish between configuration files that are shared by all Koha sites on a server and which are not.
For example, on a Git install you can assume that all Zebra configuration files live under $configdir/zebradb/, but the Debian package puts some in a shared /etc/koha/zebradb/ directory and some site-specific ones (e.g., zebra-biblios.cfg) under /etc/koha/sites/$SITE.
I'm not following the thread so I'm not sure the scenario is similar, but you could take a look at how 'docdir' is handled. Regards To+