-
Notifications
You must be signed in to change notification settings - Fork 3
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
How about removing your gem from rubygems? #3
Comments
I think a better solution would be to add a post-install message, explaining what had just happened. For example, a warning about which version of bundle you installed would be nice. At the time of writing this: |
What's wrong with letting people realize it's bundler and not taking away their chance to learn it properly? The existence of this gem is more confusing than anything else. |
Agreed with this. Was installing |
An error message would be more useful than this package. |
Better that this gem exists than something malicious with the same name. |
I agree with you that
gem install bundle
is annoying, but it would be less so if the user got an error about the gem not being found rather than the standard "installed" message.The text was updated successfully, but these errors were encountered: