rbenv (0.4.0+debian1-2) unstable; urgency=medium

  This release removes the rbenv-alternatives plugin. Since the Debian Ruby
  maintainers decided to not maintain multiple versions anymore, this plugin
  lost its purpose.

  Note that it's still possible to switch between the Debian provided Ruby and
  the ones you installed by yourself because rbenv already supports that.

 -- Antonio Terceiro <terceiro@debian.org>  Wed, 26 Feb 2014 13:15:21 -0300

rbenv (0.3.0-1) unstable; urgency=low

  The rbenv-alternatives plugin in this release changes the interaction
  with Rubygems: when you use the pseudo interpreters provided by `rbenv
  alternatives`, the main gems directory will be
  ~/.rbenv/versions/$version/gems instead of the system gems dir.

  - This means that `gem install` will install to this new dir, and the
    installed gems will be available for you to `require` them (of
    course, on Ruby 1.8 we have to require rubygems first).
  - Programs from gems are available through the standard rbenv
    mechanism, so they are only available if you are using the same
    rbenv version you used to install them.
  - You don't need to use sudo to install gems.
  - If you do use sudo, the gems will be installed to the system gems
    directory.

 -- Antonio Terceiro <terceiro@debian.org>  Tue, 10 Jan 2012 14:07:00 -0200
