Postmodern

I attempted to use Astaire edge with actionpack 3.0.0.rc.2, with the following hello world app: ``` require 'bundler' Bundler.setup require 'astaire' class MyController < ActionController::Base include Astaire::DSL get '/hello' do...

I just tried to run the hello world example using the latest versions of activesupport and actionpack. I ended up getting this error: ``` /home/hal/.bundle/ruby/1.9.1/bundler/gems/rails-16a5e918a06649ffac24fd5873b875daf66212ad-master/activesupport/lib/active_support/inflector/methods.rb:114:in `const_defined?': wrong constant name #...

Invoke chruby_auto before the prompt prints in interactive mode

10

@zendeavor points out that it is confusing to users that `chruby_auto` is invoked before the command is executed and before the prompt is printed. If user's (ex: @jc00ke) include `$RUBY_ENGINE`...

When populating `RUBIES`, filter out any rubies that do not contain a `bin/ruby` executable file.

Store all chruby GEM_HOMEs within ~/.gem/chruby

6

Now that chruby uses the ruby's install-dir name for the `GEM_HOME`, we should isolate all chruby `GEM_HOME` from rubygems' directory structure to prevent conflicts. This would also make cleaning-up/uninstalling chruby...

Add a `fullstaq-ruby.sh` file that adds the fullstaq-ruby-server-edition ruby paths to `RUBIES`.

Add a `chruby_foreach` function or `bin/chruby-foreach` script for running a command under each Ruby that matches the given pattern (ex: `ruby-2.`).

Properly handle gems installed via --user-install

8

When a user installs a gem with `gem install --user-install` it installs the gem into the [Gem.user_dir](https://www.rubydoc.info/github/rubygems/rubygems/Gem.user_dir) path (ex: `~/.gem/$RUBY_ENGINE/$RUBY_API_VERSION`). chruby should probably support the "user installation directory", in order...

Properly handle setting and reverting to a default Ruby

2

We need a better way to set and revert to a "default" selected Ruby. Simply adding `chruby ...` to one's `.bashrc` does not take effect after `chruby_auto` resets the current...

Use ~/.gem/$ruby/X.Y as the GEM_HOME

36

Now that [Ruby has moved to Semantic Versioning](http://www.ruby-lang.org/en/news/2013/12/21/semantic-versioning-after-2-1-0/) it means each new release will have a unique `X.Y.Z` version. Since `GEM_HOME` is defined as `~/.gem/$ruby/X.Y.Z`, this means each new release...