@thomthom said:
Does it manage existing rubys as well?
Management is not the main focus of this installer. I think if plugin installation were easier, more people would try plugins. And with an option to completely remove them, it may lower any barriers further.
I clearly don't want to clobber a users plugins folder, but that's just a matter of checking what is already there. I wouldn't know how to get information about the origin of all the files in the Plugins folder.
I do agree the issues of installation and management are closely related. But if I can get the installer installed, and developers to package for the installer, installing becomes easier for everyone, as does upgrading plugins. I want a safe and reliable installer/un-installer first.
For developers, most plugins can be "installed" from their current .zip files - it simply un-zips the archive to the Plugins folder. Beyond that, I am thinking about options for pre- and post-install scripts, as well as pre- and post-removal scripts so developers can do some preparation or cleanup if needed when their .zips are installed.