[Pkg-mediawiki-devel] Multisite install - what about DB updates?

Platonides platonides at gmail.com
Sun Jun 9 21:09:51 UTC 2013

On 03/06/13 16:01, Thorsten Glaser wrote:
> On Sat, 1 Jun 2013, Michael Gissing wrote:
>> OK, but I can't find how the .deb handles this. Packages like
>> mediawiki-extensions-openid don't have any scripts at all. How does apt
>> perform the update after installing a new version/extension?
> Not for MediaWiki at all, right now. In FusionForge, we use a trigger:
> https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=evolvis-platfrm/evolvisforge.git;a=blob;f=src/plugins/mediawiki/debian/plugin-mediawiki.triggers;h=298d5c7b96d27725a9cc7cce9e052a0d7d905d53;hb=HEAD
> https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=evolvis-platfrm/evolvisforge.git;a=blob;f=src/plugins/mediawiki/debian/plugin-mediawiki.postinst;h=1be9f3e46926044f0095f17357078436005d9253;hb=HEAD
> In the latter, the upgrade_mediawikis shell function calls the
> update.php script (with --quick) once per each target Wiki.
> I seem to remember being told by MediaWiki people that the
> upgrade process picks up (enabled) extensions automatically,
> and IIRC, I saw a table being created after enabling one and
> running update.php, once.

It does (assuming the extension follows the hooking procedure, of course).

More information about the Pkg-mediawiki-devel mailing list