On Mar 15, 2012, at 5:42 PM, Ryan Schmidt wrote: > > On Mar 15, 2012, at 13:17, Phillip Koebbe wrote: > >> If I'm following along correctly (and I very well may not be), you're >> thinking that calling 'sudo port <something>' in one terminal session is >> causing problems with RVM in other terminal sessions. Is that correct? > > I understood that he's saying that calling "sudo port <something>" in a > terminal session causes problems for rvm in that same terminal session. > >
Okay, I gave that a whirl too: [kodiak]~/Development/Projects/Self/Web/Grounect/grounect (master) $ rvm current [email protected] [kodiak]~/Development/Projects/Self/Web/Grounect/grounect (master) $ sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.0.4 installed, MacPorts base version 2.0.4 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated [kodiak]~/Development/Projects/Self/Web/Grounect/grounect (master) $ rvm current [email protected] [kodiak]~/Development/Projects/Self/Web/Grounect/grounect (master) $ Seems to work like I expect. Mac OS X 10.7.3, MacPorts 2.0.4, RVM 1.10.2. Phillip _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
