I'm trying to upgrade an installation I created using your installer quite some time ago; since your installer isn't designed to upgrade an existing installation, would you consider making your binary builds and installation source available publicly?
Yea, I could. Although the cygwin build process really is quite easy and there aren't any real gotchas...
Do you have any interest in modifying your installer to make it more "upgrade" friendly?
Big life changes so not a lot of time these days for enhancements. There are a LOT of additional gotcha one would need to handle if performing an upgrade, since cacti relies on so many different components, which many users have changed configurations over time. Thinking out loud...
- Should upgrades only be allowed if the installer was originally used or for any system?
- Should an upgrade also upgrade mysql/php/rrdtool/spine or just cacti?
- Does a user really want (or need) to download a 200 MB installer instead of a 10 MB zip and overwriting the existing cacti files manually? Nope...
- Whats the best method for reliably detecting where the Cacti files reside on both IIS and Apache installs? User input is not reliable.
- mysql upgrades can be tricky especially if there are major version changes, clustered instances, or hosted remotely.
- php upgrades can be tricky especially if there are major version changes or core php files scattered around the system (as some other installers/users do).