Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 164136 - emerge ruby doesn't install symlink named "ri" to "ri18"
Summary: emerge ruby doesn't install symlink named "ri" to "ri18"
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High trivial (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-28 00:38 UTC by Paul DuBois
Modified: 2007-01-28 02:44 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul DuBois 2007-01-28 00:38:32 UTC
emerge ruby installs a bunch of ruby programs, all having names ending in "18", plus a bunch of symlinks to them not having a name ending in "18". This is true for all the programs *except* ri18, for which no symlink named "ri" is installed.

The following information illustrates this:

/usr/bin% ls -l | grep '18$'
lrwx------ 1 root root          5 Dec 31  2004 erb -> erb18
-rwxr-xr-x 1 root root       3878 Jan 27 14:17 erb18
lrwx------ 1 root root          5 Dec 31  2004 irb -> irb18
-rwxr-xr-x 1 root root        352 Jan 27 14:17 irb18
lrwx------ 1 root root          6 Dec 31  2004 rdoc -> rdoc18
-rwxr-xr-x 1 root root       1537 Jan 27 14:17 rdoc18
-rwxr-xr-x 1 root root       1487 Jan 27 14:17 ri18
lrwx------ 1 root root          6 Dec 31  2004 ruby -> ruby18
-rwxr-xr-x 1 root root       3728 Jan 27 14:17 ruby18
lrwx------ 1 root root          8 Dec 31  2004 testrb -> testrb18
-rwxr-xr-x 1 root root        149 Jan 27 14:17 testrb18

It would be nice if a symlink named "ri" were installed as well.


Reproducible: Always

Steps to Reproduce:
1. emerge ruby
2. try to invoke "ri"
3. it doesn't work, you have to invoke "ri18"
Comment 1 Nguyen Thai Ngoc Duy (RETIRED) gentoo-dev 2007-01-28 02:28:11 UTC
What ruby and ruby-config version did you installed? Does running "ruby-config ruby18" fix your problem?
In case you are using ruby-config 0.3 or earlier, can you upgrade to >=ruby-config 0.3.1 and re-emerge ruby to see if it happens again?
Comment 2 Paul DuBois 2007-01-28 02:44:29 UTC
(In reply to comment #1)
> What ruby and ruby-config version did you installed? Does running "ruby-config
> ruby18" fix your problem?
> In case you are using ruby-config 0.3 or earlier, can you upgrade to
> >=ruby-config 0.3.1 and re-emerge ruby to see if it happens again?
> 

I have ruby-config 0.3.2, and ruby-config ruby18 did indeed fix the problem.
I apologize for not having thought of this.  I will change the bug status to
resolved.

Thanks!