>is the only problem with Extension Downloader the lack of >ability to set the location? > It's not the only problem. I have a lot of plugins installed. I keep on the bleeding edge of development. One of the problems I see is that a lot of plugins have a maxVersion check, and thus would not available for installation, even though they work with the latest SC trunk code.
I tweaked the code to just report a warning in the log if maxVersion was exceeded. Other users tweak the install.xml to get them to run. But with Extension Downloader, I guess you don't get an option - you can't install them (are they even listed?). I'd prefer it if maxVersion were only set by plugin developers if they know for certain what the max version is. Even then, the plugin may work with limited capability past the max version (some functionality may not work, but may not cause SC problems). I prefer to disable plugins (or move plugins out of the plugin folder) only if they cause problems. >Now that 7.3 is released I hope to add a >command line option to set the plugin location for extension downloader >to install to, would this fix it? > >Likely to be --extensionsdir That would be great. A prefs file setting would be good too, with --extensionsdir overriding the prefs setting. If I set that to the Server/Plugins folder, would the extension downloader be in harmony with manually installed plugins - i.e. allow them to be uninstalled/updated as if they had been installed via the extension downloader? Phil _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
