This project is archived and is in readonly mode.
commit 6f4c451 malfunctions with rvm's gemset
-
Jeremy Kemper
- State changed from new to open
- Assigned user set to José Valim
- Milestone cleared.
-
Prem Sichanugrist (sikachu)
- State changed from open to resolved
Hi Sakuro,
It seems like Carl also found this problem. He also revert the commit to use
bundlecommand without detecting the full path.So I'd mark this one as resolve. You can see the commit here: http://github.com/rails/rails/commit/7979d
-
Sakuro
So ticket #4029 `ruby1.9 rails/railties/bin/rails foo --dev` will eventually call `bundle`, i... might be re-opened...
Will using File.basename from the full path of the command solve both the problem? -
José Valim
Yes, Sakuro, using File.basename will solve the problem. Can you please give a patch? (I reopened #4029 `ruby1.9 rails/railties/bin/rails foo --dev` will eventually call `bundle`, i..., so you can post the patch there).
-
Sakuro
Caio's latest branch seems to have fixed #4029 `ruby1.9 rails/railties/bin/rails foo --dev` will eventually call `bundle`, i... and #4100 commit 6f4c451 malfunctions with rvm's gemset.