Remove bin/rspec to prevent executable conflicts with RSpec #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The bin/rspec executable isn’t needed and causes naming conflicts when other gems or applications use RSpec. Removing it clarifies the gem’s purpose and avoids ambiguity in which rspec command is run.
Resolves the following message when including the gem in an application that also includes the rspec gem: “The rspec executable in the rspec-core gem is being loaded, but it's also present in other gems (rock_rms). If you meant to run the executable for another gem, make sure you use a project specific binstub (bundle binstub <gem_name>). If you plan to use multiple conflicting executables, generate binstubs for them and disambiguate their names.”