[Rubyinstaller-devel] question on bat files
will at hotgazpacho.org
Sat Jan 31 19:10:35 EST 2009
FWIW, MS Visual Studio installs a bunch of CLI tools, but does not add
them to your path. Instead, they provide cmd/bat files that set a
bunch of environment variables and mess with the path before dumping
you to a command prompt. That way, you get a little sandbox; the env
vars and path alterations apply only to that command session.
You might want to look at that approach; one cmd file to launch 1.8.6,
one for 1.8.7, etc.
Sent from my iPod
On Jan 31, 2009, at 3:05 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
>> Are too obscure and contains lot cruft that I personally will like to
>> avoid. Being one of those having two interpreters in the path at the
>> same time (with the exact same name).
> So you're saying just leave it be, is that right?
> The only functionality I'm losing currently is that is c:\ruby18\bin
> is in the path, I can't run
> without taking it out of the path first.
> I guess you may have a point though--how many people are going to have
> more than one version of ruby installed and be using both
> Then again maybe people would do that with 1.8.6 and 1.9, so they can
> go back and forth between the two, so it could crop up.
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
More information about the Rubyinstaller-devel