Artem Melnikov wrote in post #1033575:
Hi
You may create file .rvmrc in your project directory
with such content:
"rvm use 1.9.2"
or with gemset
"rvm use 1.9.2@my_project_gemset"
Excuse my ignorance but where should I create this file? Sorry.
If it "goes back" to the *system* Ruby, you're not invoking rvm at all.
Re-read the rvm installation guide and make sure you've configured
your .bash_profile properly.
This is what i currently have in my .bash_profile
[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm" #
This loads RVM into a shell session.
Is there something else that need to be added?
Thanks a lot for your help
···
--
Posted via http://www.ruby-forum.com/\.
If you do decide to rm the MacPorts Ruby you'll need to do this:
`$ sudo port uninstall --follow-dependents ruby19`
which will remove the gems associated with that version of Ruby otherwise it
won't let you uninstall ruby19.
Cheers,
Phil...
···
On 24/11/11 20:38, "Hassan Schroeder" <hassan.schroeder@gmail.com> wrote:
Did you previously install a version of Ruby using MacPorts or Brew
or something? The built-in Apple Ruby shows up as:
binaries:
ruby: "/usr/bin/ruby"
irb: "/usr/bin/irb"
gem: "/usr/bin/gem"
rake: "/usr/bin/rake"
However that /opt/local junk got there, you need to get rid of it...
--
Nothing to see here... move along, move along
Phil Dobbin wrote in post #1033614:
I'd be tempted to just uninstall ruby19 the description of which I
posted
earlier & if you used MacPorts to install rvm, uninstall that too
(you'll
have to Google the vagaries on that particular one though). I wouldn't
bother uninstalling MacPorts however. You may need it later on for other
projects.
The System Ruby, unlike the System perl, is fine to use for development
(OS
X relies heavily on perl & Apple has tweaked the configure on the OS
version), same goes for the System Python. That's OK to use too.
If, however, you installed rvm directly from its site there's no need to
mess with it. I suggest you spend an hour at the rvm site until you know
exactly what it does.
RVM was installed directly from its site, however I would like to
uninstall ruby 19 but after typing "sudo port uninstall
--follow-dependents ruby19" and entering my password I get the following
warning.
"Warning: port definitions are more than two weeks old, consider using
selfupdate"
Any idea what could I do at this point?
Again thanks a lot for being patient.
···
--
Posted via http://www.ruby-forum.com/\.
You may create file .rvmrc in your project directory
Excuse my ignorance but where should I create this file? Sorry.
Any directory you want; when you cd into it, it'll be invoked.
If it "goes back" to the *system* Ruby, you're not invoking rvm at all.
Re-read the rvm installation guide and make sure you've configured
your .bash_profile properly.
This is what i currently have in my .bash_profile
[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm"
Yes, but does it work? Do you get the expected output from the test?
08:34 ~ $ type rvm | head -1
rvm is a function
09:16 ~ $
What is the result of `rvm info` in a freshly opened Terminal window ?
···
On Thu, Nov 24, 2011 at 9:10 AM, Fily Salas <fs_tigre@hotmail.com> wrote:
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
Do just what it asks:
`sudo port selfupdate`
It won't update the MacPorts base (well, I ran it yesterday & there wasn't a
new version available) but it may come back with a list of ports that are
outdated. You can either run:
`port outdated` to see which ports have been updated & then run:
`sudo port upgrade outdated`
Or just ignore everything after the selfupdate & delete ruby19 (obviously if
a newer version of ruby19 is available you don't want to update that as
you're about to uninstall it).
Cheers,
Phil...
···
On 25/11/11 14:02, "Fily Salas" <fs_tigre@hotmail.com> wrote:
RVM was installed directly from its site, however I would like to
uninstall ruby 19 but after typing "sudo port uninstall
--follow-dependents ruby19" and entering my password I get the following
warning.
"Warning: port definitions are more than two weeks old, consider using
selfupdate"
Any idea what could I do at this point?
--
Nothing to see here... move along, move along