I've been installing from Rubygems ... but some things argue about where my gems are installed. I can put the gems bin folder in my path, and there is always one that just doesn't like it.
I guess the biggest thing is that error message ... I think maybe its the version number being part of the gem install command. "ERROR: could not find gem /opt/local/var/macports/distfiles/ruby/activesupport-2.2.2" I'm going to try and mod the Portfile so it does not include the version # in the gem install command and see what I come up with. I don't consider myself to be a dev ... but I can read and understand most languages and can search for errors, sometimes I can even fix the code -- though I couldn't explain it if asked. On Fri, Aug 6, 2010 at 1:51 AM, Ryan Schmidt <[email protected]> wrote: > > On Aug 6, 2010, at 00:34, Nathan Brazil wrote: > >> In any case, you probably want to use Rubygems to install gems instead. > > If we want people to install gems separately from MacPorts, then we should > not have any ports for gems. > > If on the other hand we want to handle this as we do for example Perl modules > from CPAN, then we do want to have ports for all the gems, and we should then > not advocate users installing them manually. > > > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
