On 15/10/12 19:57, Axel Thimm wrote:
Hi Mark,
I'm adding Patrick Uiterwijk to the Cc, as he's been attacking the package upgrade as well in the last weeks.
The main obstacle is a patch that ensured using a single codebase for multiple instances of mediawiki w/o touching/extending the LocalSettings.php configuration. The patch was splitting the use of $IP to two variables holding the code path and the data path respectively.
What patch are you using? How is it configured?
I've examined the current other solutions of doing so (e.g. as outlined on http://www.mediawiki.org/wiki/Manual:Wiki_family but none really provides a single source-multiple data solution w/ arbitrary install location for the instances and no special handling in LocalSettings.php.
You need some config switching somewhere. Perhaps the LocalSettings.php from MediaWiki POV could simply select from different subordinate LocalSettings.php
Ideally we'd modify mediawiki in Fedora/RHEL to
o allow for concurrent installs of different mediawiki versions
May I ask why would you want this? Ideally, you shouldn't ever need anything other than the latest version.
o allow simple imports/migration of unpackaged mediawiki sites w/o changes to LocalSettings.php
The custom config at the user LocalSettings.php would need to reflect somewhere in your setup.
Would it be acceptable to mediawiki devs to split the use of $IP between code and data instances? In that case we should try to patch upstream into 1.20 this change, so all distributrions could simply use a central code/multiple data farm setup.
You mean as used for locating the files and as basis for the $wg*Directory variables? Seems doable easily. Any suggestion for the name of the "data $IP" ?