Releases: boxen/puppet-ruby
Bump ruby-build for Ruby 2.1.1
7.1.1
Ruby 2.1.0 support
- Upgraded ruby-build to get the Ruby 2.1.0 definition
- Removed the alias to Ruby 2.1.0. Starting with 2.1.0 the Ruby versions will not include the patch level anymore. The next 2.1 version will be 2.1.1.
Begone, version classes!
This release's primary change is the removal of the specific version classes, e.g. ruby::1_9_3_p485, ruby::jruby_1_6_4, etc. These classes came in two varieties, both involving a whole lot of duplication which hid the actual distinctions.
The first variety was the specific version and patchlevel, like ruby::1_9_3_p485 which installed 1.9.3-p485. These would occasionally include specific environment variables for compilation, such as gcc for the 1.8.7 series, or configure flags to disable tcl/tk. The second variety specified version aliases, like ruby::1_9_3. These simply created a symlink in ${BOXEN_HOME}/rbenv/versions which pointed from the alias name (1.9.3) to a specific version (1.9.3-p484).
All of these version-specific things can now be configured via hiera. We ship all of the old customizations that were present in the version classes in a custom hiera hierarchy in the data/ directory. If you include the puppet-module-data module in your boxen repo's Puppetfile, this hierarchy will be picked up automatically. You can then override and extend the configuration in your boxen repo's own hierarchy. For example:
ruby::version::alias:
1.9.3: 1.9.3-p484
2.0.0: 2.0.0-github
2.0.0-github: 2.0.0-github6This release should be a major step forward for extensibility and flexibility of the puppet-ruby module. Your organization's choices about which ruby versions should be aliased, and how they're built, are no longer tied whatsoever to what we the maintainers of this module decide.
Add JRuby 1.7.6
6.8.0
6.7.5: Merge pull request #64 from boxen/p353
6.7.4
6.7.3: Merge pull request #61 from mnussbaum/upgrade_ruby_build
Upgrades ruby-build version and fixes two specs