
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
RubyGems
|
| Affects Version/s: |
1.2.0,
1.1.2
|
| Fix Version/s: |
1.2.0
|
|
|
In particular, when a new user is on Windows and installs the one-click installer, they'll have an old rubygems and an old rake installed. When we auto install gems, rails 2.2.2 will fail because we don't install our pre-included rake (because rake is already installed). If we were to force updates of gems where we provide newer versions optionally we'd be able to fix that. (i.e. upgrading rake is pretty safe, but upgrading rails on a user might piss them off)
|
|
Description
|
In particular, when a new user is on Windows and installs the one-click installer, they'll have an old rubygems and an old rake installed. When we auto install gems, rails 2.2.2 will fail because we don't install our pre-included rake (because rake is already installed). If we were to force updates of gems where we provide newer versions optionally we'd be able to fix that. (i.e. upgrading rake is pretty safe, but upgrading rails on a user might piss them off) |
Show » |
|
fix - Need to have auto install gems job update gems if ones we provide are newer (dependent on property?)
Force updating rake gem if user has older version installed - so users who have one-click ruby install on windows won't get error installing rails we pre-include.