#2748 Should allow overriding 'gem' command for environments with multiple ruby installs - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#2748 ✓stale

Should allow overriding 'gem' command for environments with multiple ruby installs

Reported by dwaite | June 3rd, 2009 @ 03:15 AM | in 3.x

When on Mac OS X, installing ruby 1.9 from MacPorts will add a '1.9' suffix to commands. Some Linux distributions also have such a suffix by default. However, when doing a 'rake1.9 gems:install', the GemDependency object runs the 'gem' command based solely on the ruby system string.

The attached patch adds support for a GEM_COMMAND environment variable, to allow for arbitrarily specifying the executable name (and possibly path) for running the 'gem' utility. It seems that the unix idiom for specifying such things is the tool name in caps (i.e. CC=gcc). However, 'GEM' is already used to specify a specific gem name by the rake 'gem:' tasks.

0001-Add-GEM_COMMAND-environment-variable-to-allow-for-ov.patch 2.4 KB

Comments and changes to this ticket

You flagged this item as spam.
dwaite June 3rd, 2009 @ 03:22 AM
the test is insufficient as it depends on the current working directory. I created a local variant which uses:
```
ENV['GEM_COMMAND'] = "touch #{filename};#"
```
However, I do not know if such unix shell gymnastics are suitable for tests.
You flagged this item as spam.
dwaite June 3rd, 2009 @ 11:47 PM
- Tag set to “patch”
You flagged this item as spam.
dwaite June 4th, 2009 @ 05:25 AM
Based on feedback, revised testing to just call gem_command vs. invoking a script/command.
- 0002-Add-GEM_COMMAND-environment-variable.patch 2.1 KB
You flagged this item as spam.
dwaite June 4th, 2009 @ 05:26 AM
(probably bad naming convention on my part; that is a new patch and is not meant to be installed in-order)
Jeremy Kemper May 4th, 2010 @ 06:48 PM
- Milestone changed from “2.x” to “3.x”
[bulk edit]
Rohit Arondekar October 9th, 2010 @ 04:07 AM
- State changed from “new” to “stale”
- Importance changed from “” to “”
Marking ticket as stale. If this is still an issue please leave a comment with suggested changes, creating a patch with tests, rebasing an existing patch or just confirming the issue on a latest release or master/branches.
Ryan Bigg October 9th, 2010 @ 09:55 PM
- Tag cleared.
Automatic cleanup of spam.
Jeff Kreeftmeijer November 8th, 2010 @ 08:48 AM
Automatic cleanup of spam.