
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
RubyGems
|
| Affects Version/s: |
1.0.0
|
| Fix Version/s: |
1.0.0
|
|
| Importance: |
Major
|
| Studio Install Type: |
N/A
|
| Operating System: |
Mac OS X
|
| Participants: |
Chris Williams
|
|
Leopard installs gems into two directories - system where they have pre-installed gems, and a user directory. Our variable loadpath initializers only support resolving a variable to a single path. We need to be able to get the whole path to resolve it and check each of the locations the gem could be installed.
|
|
Description
|
Leopard installs gems into two directories - system where they have pre-installed gems, and a user directory. Our variable loadpath initializers only support resolving a variable to a single path. We need to be able to get the whole path to resolve it and check each of the locations the gem could be installed. |
Show » |
|
What this does is allows us to have multiple gem install paths, but use the same variable to refer to both. Then we can resolve them to their correct file system paths regardless of whether there's one or 20 possible install paths (so long as the gem is installed). This also means we're still portable across different machines.