[geeklog-devel] Autoinstall plugins and dependencies
vfuria at gmail.com
Fri Oct 2 21:28:06 EDT 2009
Are there any plugins out there (yet) that require another plugin to be
installed? While its certainly something that should take into account going
forward, are we borrowing trouble addressing an issue that doesn't exist
On Fri, Oct 2, 2009 at 2:54 PM, Randy Kolenko <Randy.Kolenko at nextide.ca>wrote:
> The autoinstall for plugins is a great way to eliminate the manual
> install process and to facilitate the upload of plugins.
> However there are some functional aspects of the autoinstall process
> which need to be addressed. In particular the idea of plugins which
> have dependencies on other plugins.
> For example, if Plugin A depends on Plugin B being installed, there is
> no way with the autoinstaller to notify the end user that their plugin A
> needs to have Plugin B installed first.
> We need to have a change to the plugin install routine to have a
> preliminary installation check done first so that the plugin being
> installed has the chance to check for dependencies, and return friendly
> error messages.
> This augmentation needs to behave with the fresh/clean installation of
> geeklog as well in the event plugins are bundled with a distribution.
> That means that a prerequisite test should not disrupt the clean
> installation of plugins during a fresh install and should gracefully not
> install themselves.
> I suggest having a plugin_autoinstall_prerequisite_pluginname function
> in the autoinstall.php file that would carry out the dependency checks
> and return status/message codes. On a geeklog fresh install, those
> status/error codes can be dumped to the error log, and on manual
> installs, they can be displayed as error messages in the plugin admin
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geeklog-devel