| Thread Previous • Date Previous • Date Next • Thread Next |
Currently the one bit of dependency management Mahara has, is the "live-
in" blocktypes that live under artefacts. In Bug 1521418 I'm discussing
getting rid of those. If we did that, then adding explicit plugin
dependencies like this would become more important.
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1299908
Title:
Let plugins specifify dependencies and version requirements
Status in Mahara:
Confirmed
Bug description:
See forum discussion:
https://mahara.org/interaction/forum/topic.php?id=6191
Sometimes we have plugins that depend on the existence of other
plugins, and they have to be installed after them. Or, we might have
plugins that depend on other plugins (or the system itself) being at a
certain version number.
We could make this happen by adding (optional) version requirements to
the plugin's version.php file. It would look like this:
$config = new stdClass();
$config->version = 2014033100;
$config->release = 1.0.0
$config->coreversionrequired = 2014032700;
$config->pluginsrequired = array(
'artefact.blog' => 2011091400,
'notification.email' => 2008040200,
);
Part of the installation process would be to check all the plugins
that are queued for installation and rearrange the installation
sequence if some of them are dependencies of others.
This would complement the sanity check method also proposed in
https://bugs.launchpad.net/mahara/+bug/1298855
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1299908/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
