-1 old installer +1 gem > gem install watir
Easy peasy. I have used cvs co, old installer, new installer and the gem. The gem installation was simple. I especially like the fact that it only installs watir. The only issue was having to (manually) remove watir from lib\ruby\site_ruby\1.8 before using the gem installation. If you continue with the old installer for people installing from HEAD, I suggest that you make it a simple mkpath/install type script that just installs watir. I would prefer to see dependencies like AutoIt moved out. Like Ruby itself, I can download and install AutoIt before installing Watir. It should just be referenced as a (possible) dependency in the Installation instructions. Thanks to the Watir development team for all the hard work. It's a great tool. -sean -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bret Pettichord Sent: Wednesday, August 31, 2005 8:38 PM To: [email protected] Subject: [Wtr-general] new installers Our new installers have been out for a bit. And we need to update our docs to reflect this. Should we tell people about the one-click installer, the gem or both? We have scattered reports of problems with the new one-click installer. We'd appreciate hearing more about it? Is it working for you. Do you like it? Is it better than the old one. I want to update our documentation on how to install Watir and would like some feedback first. I am also planning to convert the old installer to be a simply command line installer -- that way we have something very reliable for people who want more than a gem and are having problems with the one-clicker or want to install directly from HEAD. Bret _____________________ Bret Pettichord www.pettichord.com _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
