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

How about removing your gem from rubygems? #3

Open
KevinBongart opened this issue Jan 5, 2015 · 5 comments
Open

How about removing your gem from rubygems? #3

KevinBongart opened this issue Jan 5, 2015 · 5 comments

Comments

@KevinBongart
Copy link

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.

@tom-lord
Copy link

tom-lord commented Feb 9, 2015

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:
gem install bundle --> installs bundler-1.8.0.pre
gem install bundler --> installs bundler-1.7.13

@nkgm
Copy link

nkgm commented Nov 26, 2015

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.

@tlunter
Copy link

tlunter commented Dec 7, 2015

Agreed with this. Was installing bundle and it was installing 1.11 beta 2 which was causing all sorts of problems.

@tom-jin
Copy link

tom-jin commented Jan 11, 2016

An error message would be more useful than this package.
If someone is mistakenly trying to update bundler by running gem install bundle the package is not updated when bundle is installed.

@michaelkirk
Copy link

Better that this gem exists than something malicious with the same name.

https://news.ycombinator.com/item?id=11862217

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

6 participants