|
From: Colin B. <Col...@as...> - 2001-11-20 02:54:44
|
Now that Patrick is starting to look at the build process we all need to think about how we want to deploy plugins. One of the important things about plugins is that they can be downloaded separately from the main Squirrel distribution and then installed. The question is how should that installation process occur?. One method would be to simply unzip/untar the deployment file into the <squirrel_app>/plugins folder hoping that they remember to use the "use folder names" option. This has the advantage of simplicity from our point of view but isn't real friendly. It also doesn't give us the option of running any code at installation time although its debatable whether or not we should, rather any first-time code should be run on the first execution of a plugin. Another possibility would be creating a IzPack installer for each plugin. When the installer is run it would default to the install directory for Squirrel (we would need to modify IzPack for this) unpack the plugin into the appropriate directory structure etc. As well we need to think about how we want the plugins to appear on the SourceForge downloads page. I don't like the idea of each plugin having its own package. Once you have a few plugins each with a few releases it would get quite messy. I quite like the Jext method http://sourceforge.net/project/showfiles.php?group_id=1494 Here there is a single package for all the plugins, each plugin has its own release. This has the advantage of keeping everything simple. Possibly the only change I would make would be putting the plugin release number as part of the release name. This would make it easier for people to see whether a new release has occurred. Any ideas, comments? |
