rake gems:install only installs one gem at a time
Reported by Tim Morgan | May 16th, 2008 @ 08:08 PM
If an app indicates four gem dependencies, and none are installed, doing a rake gems:install will install the first gem and exit. Thus one has to run the task four times.
The problem seems to come in here: http://github.com/rails/rails/tr...
Gem::GemRunner.new.run(install_command) does not return to the running task; it instead exits.
Comments and changes to this ticket
-
Tim Morgan May 16th, 2008 @ 09:14 PM
- no changes were found...
-
Tim Morgan May 16th, 2008 @ 10:06 PM
Possible fix here: http://github.com/seven1m/rails/...
Will someone pull into official rails repo?
-
Tim Morgan May 16th, 2008 @ 09:11 PM
Here's a patch in case that is easier than doing a pull. Thanks.
-
Tim Morgan May 16th, 2008 @ 09:14 PM
Weird: my patch file is not showing up on this issue, and my first comment pointing to my commit on my forked Rails repo is marked as spam.
Let's try again: Commit with fix lives here: http://github.com/seven1m/rails/...
The patch should be attached.
-
DHH May 31st, 2008 @ 09:33 PM
- → Assigned user changed from “” to “rick”
-
Repository May 31st, 2008 @ 11:59 PM
- → State changed from “new” to “resolved”
(from [fb89d7fa6d21a4b0faab753ff3a7c934d9d59883]) Run gem install as external command. [#210 state:resolved]
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
rick