On Oct 6, 2009, at 1:29 AM, Vornoff Jungle wrote:
The instructions at the second link seem to be more promising, but I encountered an odd error when I tried to run 'gem', 'gem -v', etc."gem1.8" works fine for "gem" and "gem1.8 -v" returns 1.3.1.Possibly the best solution is to either copy or make a symbolic link from gem1.8 to gem in /usr/bin.
That would seem like a good idea. Presumably, /usr/bin/gem is supposed to be a symbolic link to the correct executable.
After that, I still only have "gem1.8," not "gem," but I tried going back to instiki and running it again. At this point it runs, and I was able to create a wiki.
Instiki does not care whether you have the commandline "gem" utility installed correctly. Rail (the version bundled with Instiki) does care that the Rubygems libraries (1.3.x) are installed correctly. That seems to have succeeded for you.
The next question is whether I have gem messed up, and whether it should be fixed, or whether I should ignore it and carry on with using instiki.
Instiki doesn't care. BUt you might want to be able to type "gem", rather than "gem1.8".
JD
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
