marekj
Fri, 20 Jul 2007 08:09:38 -0700
Thanks. I wasn't aware that gem command scans working dir first. Here it is "gem install... It will attempt a local installation (i.e. a .gem file in the current directory), and if that fails, it will attempt to download" http://rubygems.org/read/chapter/10#page33 Note to self: read instructions and installation notes. thanks. marekj On 7/20/07, Bret Pettichord <[EMAIL PROTECTED]> wrote:
marekj wrote: > One word of caution with downloaded gems. > Use 'gem install watir --local' option to to pick up the downloaded > gem and not the --remote > Actually, this only matters if you didn't actually download the gem to the current directory. _______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
_______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
- [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again vipin
- Re: [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again Željko Filipin
- Re: [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again marekj
- Re: [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again Bret Pettichord
- Re: [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again vipin
- Re: [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again vipin
- Re: [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again vipin
- Re: [Wtr-general] Installing watir 1.5 actually installs 1.4.1 again Ajitesh Srinetra