Fix and spec for bug handling relative paths in Gemfile.

[mbirk]

If a Gemspec contains a gem requirement with a version and :path option with a relative path, then the path will be resolved relative to the current working directory, rather than the Gemfile. For example:

gem 'rails', '2.2.3', :path => 'vendor/rails'

According to the Gemfile(5) spec (http://gembundler.com/man/gemfile.5.html):

"PATH (:path) ... Relative paths are resolved relative to the directory containing the Gemfile."

This pull request provides a fix for this bug, as well as a spec that demonstrates the issue.

[indirect]

Looks like it, yep. I believe up until now I have been using paths in the form ./vendor/rails, which will work without this patch. Thanks!

[indirect]

This spec turned out to break all specs that ran after it, because it modified the process running rspec instead of shelling out to a child ruby process like all the other specs do. Fixed in 2dc3f80.

[mbirk]

Ack, my bad, thanks for quickly accepting the bug fix and cleaning up
the spec!

On 5/11/11 1:04 AM, indirect wrote:

This spec turned out to break all specs that ran after it, because it modified the process running rspec instead of shelling out to a child ruby process like all the other specs do. Fixed in 2dc3f80.