<div dir="ltr">Hi,<div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 24, 2013 at 12:54 AM, Mathieu Saby <span dir="ltr"><<a href="mailto:mathieu.saby@univ-rennes2.fr" target="_blank">mathieu.saby@univ-rennes2.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff" text="#000000">
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?<br>
So it could be used by my patch and probably by others.<br></div></blockquote><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div> </div></div>Regards,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Galen<br>-- <br><div dir="ltr"><div>Galen Charlton</div><div>Manager of Implementation</div><div>Equinox Software, Inc. / The Open Source Experts</div>
<div>email: <a href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a></div><div>direct: +1 770-709-5581</div><div>cell: +1 404-984-4366</div><div>skype: gmcharlt</div><div>web: <a href="http://www.esilibrary.com/" target="_blank">http://www.esilibrary.com/</a></div>
<div>Supporting Koha and Evergreen: <a href="http://koha-community.org" target="_blank">http://koha-community.org</a> & <a href="http://evergreen-ils.org" target="_blank">http://evergreen-ils.org</a></div></div>
</div></div>