[geeklog-devel] Autoinstall plugins and dependencies

[Randy Kolenko]

I thought about having the dependency idea as well as you noted.
That, in fact, could be part of the return array in the
plugin_autoinstall_pluginname function.
This way the autoinstaller can detect if those specific plugins are
installed or not and then bail out of the install with messages
signifying those plugins are not installed.

Perhaps that is a "simpler" way to do this?

-randy





-----Original Message-----
From: Vincent Furia [mailto:vfuria at gmail.com] 
Sent: Saturday, October 03, 2009 11:38 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] Autoinstall plugins and dependencies


Is there a reason why:


Our plugins today, have a pre-install hook that is called on install and
checks if the dependencies like other plugins, directories, perms etc
are tested before allowing the install to proceed and we show the site
admin the status of the pre-requisites.


Isn't sufficient?

Would a dependency array work better.

PluginA_Required = array('PluginB', 'PluginC');.

With that information the autoinstaller could be made to be smart enough
to generate a dependency tree and install multiple plugins in order.
Other "preinstall" checks (file permisisons, etc) could be accomplished
in the install function.

-Vinny


On Fri, Oct 2, 2009 at 9:38 PM, Blaine Lang <devel at portalparts.com>
wrote:

Vincent Furia wrote:

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 yet?


Yes, several of the nexpro suite plugins have dependencies on other
plugins. Most of the plugins are dependand on the nexpro core plugin and
others need the nexlist plugin. The nexflow plugin uses the nexform
plugin for creating forms and routing them for review and approval. The
nexproject plugin needs nexfile and nexforum.,

Our new release will be using the core nexpro plugin to manage even more
common code and config options online for the other plugins. Our plugins
today, have a pre-install hook that is called on install and checks if
the dependencies like other plugins, directories, perms etc are tested
before allowing the install to proceed and we show the site admin the
status of the pre-requisites.

The autoinstall feature works well but is missing this ability. The
autoinstall should check if a plugin has 'preinstallcheck' function, and
allow that plugin to return more then a status or message. It should
optionally be able to return a formated page - that can display status
of any requirements. The autoinstall needs to have an fully automatic
mode that is invoked if a plugin archive is uploaded or when geeklog is
being installed - as it is now. The autoinstall is also invoked if you
do a normal individual plugin install and  there should be an option of
calling a preinstall function to display a splash page or into page
before proceeding with the manual install. This function can also
display the results of any preinstall checks.

It also would be nice if there was a way to control the order plugins
are installed.

So in summary:
- autopreinstall($mode)
- if mode ==  'automatic' then just return a status and message.
- if mode == 'manual' then return a status and formatted page

Blaine

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel