[geeklog-devel] we don't need to maintain the plugin's upgrade function

Michael Jervis mjervis at gmail.com
Thu Mar 20 03:28:41 EDT 2008

Just roughly, but, in what scenario would you need the upgrade
function that isn't covered by the Geeklog installer for a currently
bundled plugin?

I don't have them installed, I don't need the upgrade.
I have them installed, they are upgraded by the install.

They aren't released separately, so there is no need for the
individual upgrade function unless we make a plugin release
independantly to the main software.

Or have I lost the plot?

On Wed, Mar 19, 2008 at 8:16 PM, Joe Mucchiello <joe at throwingdice.com> wrote:
> At 05:12 PM 3/17/2008, Dirk Haun wrote:
>  >Log Message:
>  >Plugins are updated by the install script, so we don't need to
>  >maintain the plugin's upgrade function
>  What? Why not disable editing them in the plugin menu too? I thought
>  you were planning to decouple the plugins from the core tarball.
>  That's where I thought the PEAR deployment stuff was headed. This is
>  a serious blow toward PEAR delivery ever working with selectable plugins.
>  Okay, I read back a few days and see you did discuss this. But the
>  reason those functions were hard to maintain was because the
>  installer cheats. If you can maintain the upgrade_linksplugin
>  function in install.php why can't you move that functionality to
>  links/functions.inc and call plugin_upgrade_links instead?
>  Too late now I suppose.
>  ----
>  Joe Mucchiello
>  Throwing Dice Games
>  http://www.throwingdice.com
>  _______________________________________________
>  geeklog-devel mailing list
>  geeklog-devel at lists.geeklog.net
>  http://eight.pairlist.net/mailman/listinfo/geeklog-devel

Michael Jervis
mjervis at gmail.com

More information about the geeklog-devel mailing list