I advice at the beginning not to overdo the 'mix and mach' with rvm. Start with just having all your old gems at the new ruby/gems version.
to do that first switch back to your system gems: > rvm system export gems to a file > rvm gemset export mygems this will write a file 'mygems' in the current directory now switch back to your new version (and make it default if you din't already): > rvm --default 1.8.7 and import the gemset: > rvm gemset import mygems This should go and install all your old gems in one go. On May 21, 9:08 am, Chris McCann <[email protected]> wrote: > Peter, > > After reading about the project-specific .rvmrc file I definitely see > the benefit of that approach. The one thing I haven't figured out, > though, is how to make rvm aware of all the gems that are currently on > my system. I really don't want to install all of them again. > > I tried the last example athttp://rvm.beginrescueend.com/workflow/examples/ > about installing gems from the system directory but it's not working > and I suspect it's because of the changes I made in trying to get > 1.8.7 running. When I run the "rvm system" command and then "rvm > info": > > system: > > system: > uname: "Darwin Chris-Macbook.local 9.8.0 Darwin Kernel > Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/ > RELEASE_I386 i386" > shell: "bash" > version: "3.2.17(1)-release" > > And this isn't what I expected at all, so something is amiss. > > I'll keep digging. > > Chris > > > The killer feature in RVM is gemsets. Just drop a .rvmrc file in a project > > folder and when you cd to that folder it will automatically change to the > > defined ruby version and gemset for that project. > > > So... > > > % cd /path/to/my/rails3project > > Using ruby 1.9.2 head with gemset myrails3project > > [master]% > > > Have fun, > > Peter > > -- > SD Ruby mailing list > [email protected]http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
