On 01/08/2012 09:14 PM, Antonio Terceiro wrote:
Also, note that when you call `gem1.8`, your are specifically requesting
ruby 1.8, so there is not much we can do to stop the program installed
from runninnd under ruby1.8
rbenv can only help you (with the approach I proposed in the previous
message) if you call `gem` and without sudo.
That is true, but as it currently works, running gem without sudo complains
(rightly) that it cannot write in the global gem directory. This is why I had to
resort to calling gem1.8 directly with sudo. Your proposed solution would
thankfully make this unnecessary.
Kind regards,
--
Matijs
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers