I dug a bit into the history and found a couple things:
- build/tools/update.sh is no longer a factor; it's a helper script to assist with upgrades on a developer installation of Evergreen, but it hasn't been touched in years. We should probably remove it.
- However, time was that autogen.sh did have a parameter for specifying the location of opensrf_core.xml. However, that was dropped in 2011 on the basis that OpenILS/Utils/Cronscript.pm gets updated during installation with the path to opensrf_core.xml.
However, it is no longer a safe assumption that Cronscript.pm always points to the proper location of opensrf_core.xml; Equinox at least runs multi-tenant Evergreen setups that operate with a shared PERL5LIB but separate opensrf_core.xml configs.
This does suggest a cautionary note during upgrade: if you're running with opensrf_core.xml located anywhere other than /openils/conf in a single-tenant manner, make sure that SYSCONFDIR as set in autogen.sh matches what's set in the installed Cronscript.pm.
I dug a bit into the history and found a couple things:
- build/tools/ update. sh is no longer a factor; it's a helper script to assist with upgrades on a developer installation of Evergreen, but it hasn't been touched in years. We should probably remove it. Utils/Cronscrip t.pm gets updated during installation with the path to opensrf_core.xml.
- However, time was that autogen.sh did have a parameter for specifying the location of opensrf_core.xml. However, that was dropped in 2011 on the basis that OpenILS/
However, it is no longer a safe assumption that Cronscript.pm always points to the proper location of opensrf_core.xml; Equinox at least runs multi-tenant Evergreen setups that operate with a shared PERL5LIB but separate opensrf_core.xml configs.
This does suggest a cautionary note during upgrade: if you're running with opensrf_core.xml located anywhere other than /openils/conf in a single-tenant manner, make sure that SYSCONFDIR as set in autogen.sh matches what's set in the installed Cronscript.pm.