Win32 Install - How About A Single MSI / Package? read on..

[NextLevel]

I've noticed that the install routines are different, both on the CACTI site itself and on one of it's valued members (2600 site).

While appreciated, it's obviously somewhat irritating that the primary method to get this working in a Win32 environment is a hacked collection of confusing and disparate documentation.

NO OFFENSE MEANT -- but I know this has probably irritated others. And while I do know that people have jobs and full time responsibilities, and this is primarily a labor of love for those involved -- it can be made better. And, yes, I'm willing to step up to the plate and try to tackle this.

I have a suggestion: I'd like to put together a working group of two or three individuals that can produce a monthly .MSI for Win32. This would be a simple endeavor at first, possibly putting together a minimal collection of supported install bases (Win32 2K3/2000, All Editions, etc). It could grow over time, include 64bit and various combinations of various components, but I think we should stick to a common combination of packages that are well tested for now.


Anyone familiar with AutoPatcher http://www.autopatcher.com? This Neowin-sponsored project is the same type of mentality I have and I realize while that the continuous (quarterly if not monthly) update of the packages for this project would be required, I think it'd be an effort worth while. I mean, 5 minutes to Cacti on Win32 (versus 5+ hours and counting [still doesn't work] on my box?) Yah, I think that'd be an effort well appreciated.

Granted, there are probably 20-30 variables we'd have to define and create situations for, but I think it's doable.

I'm willing to host a separate site, code, a CVS, offer up development tools (I have extensive amounts) and hell, even some virtual machines if I can find the time to rebuild my server. Well, don't let me get too far -- I do need help.

I'd love to have thoughts, comments and ideas.

Thx

[BSOD2600]

Yes, you're right Cacti is not a plug-n-play program and does take some time to configure. Why rony hasn't updated the installation guide in the cacti site (again) with my guide (which works), I don't know. Probably a lack of time.

I've actually already put together an automatic installer for Cacti using NSIS and all the latest required packages. In the spirit of cacti being open source / free, it would be better if that was used instead of an MSI packager. The all on one installer has not been made public for two reasons (that I'm aware of). 1) It currently only works if you install it on the C: drive (this is because I'm manually importing registry entries instead of scripting the registry entry creations). 2) rony hasn't put it up on the cacti site (why, I have no idea).

I've set up a VMware XP Pro OS, where I have all the various packages set up, which I use to build the NSIS package. If you have the time / energy, I could give you the nsis script for you to further devolop (but IMO it's already functioning just fine on the serveral OS'es and people that have tried it).

[cybertron]

I have a great interest in this as well, is it possible for me to get ahold of the NSIS package? I am not a programmer, and wont be able to edit it any, but I have no problem installing on C drive.

[BSOD2600]

Set up an FTP account and I can upload it to you.