That would probably be the best solution in the interim. I personally install all of my MacRuby gems in ~/.gem/macruby/1.9.0 (which is the default directory if you don't run macgem under sudo). This way /usr/bin is not altered and when I want to run a MacRuby gem helper I simply append ~/.gem/macruby/1.9.0/bin to my $PATH. Laurent On Nov 2, 2009, at 12:06 AM, Eloy Duran wrote:
I think the best solution would be if RubyGems would apply the same program prefix or suffix to the executables it installs. So in the case of MacRuby, the executable would be: /usr/bin/macspec.
I haven't had the time to look at RubyGems yet though, if anyone wants to take a stab at fixing this, by all means :)
Eloy
On 2 nov 2009, at 08:40, Matt Aimonetti wrote:
Unfortunately this is not an issue with MacRuby, you would have many issues with ruby1.9 or any other implementations.
- Matt
On Sun, Nov 1, 2009 at 10:52 PM, s.ross <cwdinfo@gmail.com> wrote: When installing the gem using macgem, a shebang line is written pointing to macruby. The "spec" binary copied into /usr/bin forever after (or until manually edited or reinstalled) contains that shebang. Until MacRuby is close to parity with MRI (say... when MRI can run Rails), this may make less difference. Now, however, the single-location binary can cause a problem.
I'm not sure what a sensible solution is to this, but thought since rSpec is getting some attention, I'd bring this up.
-s _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel