Is this a bug in RVM or MacPorts?

[Phil Dobbin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24/03/2012 23:34, Behrang Saeedzadeh wrote:
> Hi all,
> 
> I recently installed the latest version of RVM, and it caused ~/.profile
> not to be sourced anymore. A discussion ensued here
> (https://gist.github.com/2182557#comments) and it turns out that RVM
> creates two files |~/.bash_profile| or |~/.bash_login| and consequently
> ~/.profile is not getting sourced anymore.
> 
> Could you guys please read the discussion in that thread
> (https://gist.github.com/2182557#comments) and see if this is an RVM bug
> or a MacPorts bug?


If you search the list archives over the last couple of weeks, I've also
encountered this conflict between Mac Ports & rvm.

I've spoken at length both here & on the rvm list about it & it does
just seem to be a conflict not a bug in either Mac Ports or rvm.

Anything that is vying for your $PATH is bound to conflict with anything
else that is trying to do the same.

FWIW, I've eliminated it down to only it causing a problem when sourcing
the bash_profile from within an already open window otherwise everything
behaves as it should.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

	Wm. Shakespeare - Much Ado About Nothing


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPbmWzAAoJEKpMeDHWT5ADbEgH/0guvMyGhvMOf4nGnRm0mtJ4
wVF0Y4Q/pNcAt9WrzcuyD9UG3cIHGBkeYxsusLuXHXuJ6mJEjG1+tlxUO44fybRl
NVDT3rnlUrFtMvWFRzoKxtemr+9yFDsatcBwxWZ98T89YoNMlJbEAahT7q+I4DKR
c22YfWeGX/VVtx2zEluQ8OWzoNfoOH1J7sWrWQm0tkaRnCkQgJ6O+UePv93BVAJy
jRj1nt/bF795u6cIPtV+SzaIjmZklYS+hOfnMzb6watUZ9vBaSJxt8rhIYVEsnPw
bOi8+aaycaEFAb+lD/Hz2WDgfcs6Y34J9lJLr5hSPIQwQe5y78rfdcFmkii/btg=
=EVI1
-----END PGP SIGNATURE-----