Chad Woolley's blog

[ANN] GemInstaller 0.5.3 Released
edit Posted by Chad Woolley on Tuesday August 25, 2009 at 11:25PM

This fixes several bugs that people have complained about for quite a while. Please let me know if anything is broken.

GemInstaller 0.5.3 has been released!

0.5.3 / 2009-08-25
Many long overdue bugfixes and patches, see http://tinyurl.com/geminstaller-0-5-3-release for details.
Thanks to Greg Fitzgerald, Britt Crawford, John Trupiano, Gabriel Gironda, and Eric Hodel for patches and assistance.
Issues with case statement under Ruby 1.9
GemInstaller cannot distinguish between gems that have the ame name but capitalized differently.
add ./ci as default location for config file
Disable GemInstaller install in default rails preinitializer.rb, but fork if it is used
autogem() fails when run for newly-installed gem
Sometimes installing fails due to RubyGems cache not being cleared between multiple API calls

Automated Gem installation, activation, and much more!

GemInstaller provides automated installation, loading and activation of RubyGems. It uses a simple YAML config file to:

Automatically install the correct versions of all required gems wherever your app runs.
Automatically ensure installed gems and versions are consistent across multiple applications, machines, platforms, and environments
Automatically activate correct versions of gems on the ruby load path when your app runs ('require_gem'/'gem')
Automatically reinstall missing dependency gems (built in to RubyGems > 1.0)
Automatically detect correct platform to install for multi-platform gems (built in to RubyGems > 1.0)
Print YAML for "rogue gems" which are not specified in the current config, to easily bootstrap your config file, or find gems that were manually installed without GemInstaller.
Allow for common configs to be reused across projects or environments by supporting multiple config files, including common config file snippets, and defaults with overrides.
Allow for dynamic selection of gems, versions, and platforms to be used based on environment vars or any other logic.
Avoid the "works on demo, breaks on production" syndrome
Find lost socks.