[Rubyinstaller-devel] [ANN] pik 0.0.2 Released

Gordon Thiesfeld gthiesfeld at gmail.com
Sat Jun 6 09:21:15 EDT 2009


On Sat, Jun 6, 2009 at 7:50 AM, Roger Pack<rogerdpack at gmail.com> wrote:
> Interesting.
> I might well end up using this :)
>
> I wonder if one difficulty is that currently open console windows
> remain fixed to the old ruby version.

Pik already updates the currenlty open console window by updating the
path to the new version.

C:\>pik sw 185 && ruby -v && rake -V
Switching to 185: ruby 1.8.5 (2006-12-25 patchlevel 12) [i386-mswin32]

ruby 1.8.5 (2006-12-25 patchlevel 12) [i386-mswin32]
rake, version 0.8.7

C:\>pik sw 186 mingw && ruby -v && rake -V
Switching to 186: ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]

ruby 1.8.6 (2009-03-31 patchlevel 368) [i386-mingw32]
rake, version 0.8.7

C:\>pik sw 191 p129 && ruby -v && rake -V
Switching to 191: ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mingw32]

ruby 1.9.1p129 (2009-05-12 revision 23412) [i386-mingw32]
rake, version 0.8.7

The --global switch will update the local session path and the whole
Windows environment.

>
> If that is the case, I then wonder if it would be possible to have
> something like...
>
> c:\ruby\bin containing
>  ruby.bat
>  gem.bat
>  run_ruby_gem_command.bat # this one takes a parameter
>
> you could always just leave c:\ruby\bin in your path, and rewrite the
> .bat files depending on which ruby you'd like to next use.
>
> run_ruby_gem_command would be like run_ruby_gem_command mongrel
> or what not.
>
> Just thinking out loud!
> -=r
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>


More information about the Rubyinstaller-devel mailing list