do not request gems declared in gemspec from rubygems

[grosser]

I'm building my own little on demand gem server and ran across the issue that bundler always requests the gem it is currently bundling in, and I'd like to avoid that overhead (in this case having to download 1 more github repo) since the information should not be used or necessary.

# Gemfile
source "http://localhost:4567/user"
gemspec

# noooo.gemspec
Gem::Specification.new "noooo", "1.0.0" do |s|
  s.summary = "s"
  s.authors = "a"
end

Resulting request from bundler:
/api/v1/dependencies?gems=noooo

[AlexandreBernard]

I may have an issue that's similar.

Updating a gem that's on rubygems with a forked one on github for dependency reasons via the git option. I see bundler checking out the gem from github but then it asks me for the old dependencies still.

[indirect]

That's actually a different issue. Please see ISSUES.

[grosser]

@Who828 did that get solved ?

[dubek]

I made an attempt to solve it in PR #3200 , but I'd like an expert opinion to make sure my change make sense (and doesn't break some other intended behaviour). Comments are welcome.

[grosser]

❤️ thx for fixing! :D