Gem dependencies can be listed in config/gems.yml
Reported by Simon Jefford | April 26th, 2008 @ 12:07 PM
For an example, see the test fixture in the patch.
Comments and changes to this ticket
-
DHH April 29th, 2008 @ 10:22 PM
- → State changed from “new” to “invalid”
Good stuff, but I don't think it belongs in core. There are not enough compelling reasons to specify your dependencies in a yml file for the general "most people, most of the time" case. Do turn it into a plugin, though.
-
Chad Woolley April 30th, 2008 @ 02:36 AM
Hi Simon,
The config.gems was originally started as a yaml file approach, but then that was decided against.
If you want a robust approach which uses a yaml file which offers some advantages over the config.gems approach, please check out my GemInstaller tool (http://geminstaller.rubyforge.org). It is working well and is used in production on several apps. I'm also very open to feedback for changes or improvement.
I plan to put up a comparison chart of geminstaller vs. config.gems, but that's going to be another month or so.
Thanks,
-- Chad
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
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
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"..
