Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation issue about gemspec name: #463

Open
sardaukar opened this issue May 17, 2019 · 2 comments
Open

Documentation issue about gemspec name: #463

sardaukar opened this issue May 17, 2019 · 2 comments

Comments

@sardaukar
Copy link

The docs say

If you have multiple gemspecs in the same directory, specify which one you'd like to reference using :name

gemspec :name => 'my_awesome_gem'

This will use my_awesome_gem.gemspec

but I've found that if I have 2 differently named gemspec files (gemname-rails3.gemspec and gemname-rails4.gemspec) and they both have specification.name = "gemname", if I use gemspec name: "gemname-rails4" on my Gemfile, it'll tell me not found. So it seems like the file name is ignored and what's used instead is the name setting on the gemspec.

@sardaukar
Copy link
Author

Which, by the way, is a bummer :D

@olleolleolle
Copy link
Member

olleolleolle commented Apr 9, 2020

Dumb question: Would it work to use gemspec :path => 'gemname-rails4'?

https://github.com/rubygems/rubygems/blob/c8890052879c23abe814b6dbb4cd8c8751f6c045/bundler/lib/bundler/source/path.rb#L25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants