Comments on: A Quick Gem (1.0.1) Faq - Gem::Runner Name Error

By: Brian

Brian — Mon, 21 Jan 2008 19:28:38 +0000

1 Thanks!

By: ben

ben — Sat, 29 Dec 2007 22:46:03 +0000

for those of you running into this using deprec with ubuntu… i think this is the fix: http://forum.slicehost.com/comments.php?DiscussionID=1140&page=1#Item_5

By: raggi

raggi — Mon, 24 Dec 2007 16:58:00 +0000

It is not “wrong”, please take a moment to understand the meaning of the word “likely” and the already posted quote from the changelog, which clearly explians how this works:

Executable stubs can now be installed to match ruby’s name, so if ruby is installed as ‘ruby18’, foo_exec will be installed as ‘foo_exec18’

Please see my updates on the original post for more information.

You may also want to spend some time looking at the documentation for your distributions package management procedures and commonalities, as Debian, like several other distributions, does this, adding the version name to a binary in order to prevent version clobbers. This is very normal, but there is no ’standard’ for it, as such FreeBSD ports follows one procedure, Debian follows another, and sometimes you’ll find that even within a distribution the package maintainers (not the original software authors, or core distribution developers), do not keep the names consistent.

A little time now could save you headaches in the future.

By: Nikolay Kolev

Nikolay Kolev — Mon, 24 Dec 2007 16:43:03 +0000

No, this is wrong. It installs it as gem1.8, not gem18… or at least on Debian 4.0 (Etch) it adds “1.8″ and not “18″.

By: antoine

antoine — Sun, 23 Dec 2007 15:54:50 +0000

thank you so much !!!!