Rename gem from bcrypt-ruby to bcrypt

[sferik]

It makes sense for this repository to be named bcrypt-ruby, to avoid ambiguity with other bcrypt libraries, but the gem name need not include -ruby, since the rubygems package manager is tightly coupled to the Ruby language. Just as the sqlite3-ruby gem was renamed to sqlite, this package’s name should just be bcrypt.

This also increases consistency between the library’s name and the way it is required.

require 'bcrypt'

I’ve also removed links to the old RubyForge project, which no longer work.

[tjschuck]

@tmm1 @codahale I'm going to move forward with this and push a new version of the gem up now unless you have any fundamental problems with this.

I'll also push a new dummy version of the gem up to the old name that depends on the new name for backwards compatibility, with a post-install message about the change.

[sferik]

Awesome! Thank you. 😄

[tjschuck]

Okay, gem has been renamed to just bcrypt and pushed up to RubyGems: https://rubygems.org/gems/bcrypt

@tenderlove @tmm1 @codahale You've all been added as owners of the new gem as well.

A new dummy version of bcrypt-ruby has also been pushed up that has bcrypt as a dependency for backwards compatibility, with a post-install message:

$ gem install bcrypt-ruby
Fetching: bcrypt-3.1.3.gem (100%)
Building native extensions.  This could take a while...
Successfully installed bcrypt-3.1.3
Fetching: bcrypt-ruby-3.1.3.gem (100%)
Building native extensions.  This could take a while...

#######################################################

The bcrypt-ruby gem has changed it's name to just bcrypt.  Instead of
installing `bcrypt-ruby`, you should install `bcrypt`.  Please update your
dependencies accordingly.

#######################################################

Successfully installed bcrypt-ruby-3.1.3
2 gems installed

[tjschuck]

@tenderlove @sferik @tmm1 @codahale Also, please consider retweeting this announcement if that's your thing: https://twitter.com/tjschuck/status/436971394333966336

Thanks!

[nirvdrum]

@tjschuck I couldn't find the source for the dummy gem so I couldn't issue a pull request. But a tiny change is "it's name" should be "its name" in the post-install message.

[accelecon]

It looks like the bcrypt-dummy gem defines the BCrypt constant and clobbers the real one.

[tjschuck]

@nirvdrum Thanks -- will fix in a jiff.

@accelecon I'm not seeing that happen... more info?

[accelecon]

It could be my fault; I'm still looking into it. My Gemfile.lock has:

    bcrypt (3.1.3)
    bcrypt (3.1.3-java)
    bcrypt-ruby (3.1.3)
      bcrypt (>= 3.1.3)
    bcrypt-ruby (3.1.3-java)
      bcrypt (>= 3.1.3)

And in rails c, I get:

irb(main):001:0> defined?(BCrypt)
=> "constant"
irb(main):002:0> defined?(BCrypt::Password)
=> nil
irb(main):003:0> 

[tjschuck]

@nirvdrum Just pushed a new version of the dummy gem to fix the typo. Thanks again.

@accelecon Here's what I've got:

$ gem install bcrypt-ruby
 [...]
2 gems installed
$ irb
irb(main):001:0> require 'bcrypt'
=> true
irb(main):002:0> defined?(BCrypt)
=> "constant"
irb(main):003:0> defined?(BCrypt::Password)
=> "constant"

Lemme know if you figure out your case, or if you have steps to reproduce.

[nirvdrum]

@tjschuck Awesome. Thanks for the quick turnaround.

[tjschuck]

@accelecon Jump over to #89 if you have any followup on the issue.