Problem with gem dependency detection of frozen gems
Reported by Tiago Macedo | July 1st, 2008 @ 12:12 PM | in 2.x
There is a problem with gem dependency in rails 2.1 and head.
If you specify your gem dependency with a <= or >= version string, the gem dependency won't detect if you have a frozen gem that isn't the specified version even if it satisfies the requirement.
Example:
config.gem "ruby-openid", :lib => "openid", :version => ">=2.0.4"
If you have ruby-openid-2.1.2 installed and type rake gems:unpack it'll freeze in vendor/gems.
However if you type rake:gems afterwards, it'll tell that it is installed and not frozen because it is looking for it under vendor/gems/ruby-openid-2.0.4 instead of vendor/gems/ruby-openid-2.1.2
What the patch does is:
Search vendor/gems for gems that match the required gem name and satisfy the required version. If more than one matching gem is found, the gem with the biggest version number is loaded.
Comments and changes to this ticket
-
Tiago Macedo July 1st, 2008 @ 12:13 PM
I didn't write any tests because this is only verifiable with frozen gems.
-
Lee Marlow July 10th, 2008 @ 12:58 PM
+1
This patch correctly detects my unpacked gems when using the ~> gem requirement syntax.
-
Lee Marlow July 17th, 2008 @ 05:21 PM
Modified the patch to not depend on ActiveSupport's String#starts_with? method
This allows starting the server via mongrel_rails, etc. instead of just through script/server
-
Pratik July 17th, 2008 @ 06:01 PM
- → Assigned user changed from “” to “rick”
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
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
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