Feature Suggestion: Add a rubygems resource.

[yfeldblum]

Feature Suggestion: Add a rubygems resource.

And an accompanying rubygems provider.

Motivation:

The user may have installed ruby and its default rubygems some time ago, but may wish to keep current with rubygems or downgrade in case of rubygems issues.

Specification:

The resource should have a required attribute ruby_string to specify which rvm-managed ruby's rubygems to change.

The resource should have an optional attribute version to specify the version constraints on the rubygems for the named ruby. The version attribute should permit an exact version, and it should also permit a version constraint, a comma-separated string of version constraints, or an array of version constraints.

The resource should have a default action of install, but also an action of upgrade.

The install action should install/upgrade rubygems into the named ruby only if a version of rubygems complying with the version constraints from the version attribute is missing.

The upgrade action should always install/upgrade rubygems into the named ruby, unless the most-recent version of rubygems complying with the version constraints from the version attribute is already installed.

[fnichol]

I've been feeling that need as well based on issues and feedback. Unfortunately, there is still a real need for 1.3.7 when supporting older codebases. Sounds good, it's on the board :)

[alindeman]

So is there a suggested way to update rubygems with this cookbook for now?

[fnichol]

@alindeman I've done this in the past which can work (although a bit lower level) in a cookbook recipe:

# assumptions:
#   * this is a system-wide install. For user-based ones use rvm::user_install
#   * the RVM Ruby to be modified is the default ruby

# include system_install which only installs RVM (doesn't install any rubies or gems)
include_recipe "rvm::system_install"

# install the default ruby from attribute metadata
rvm_default_ruby node['rvm']['default_ruby']

# use an rvm_shell to call rvm rubygems before installing any gems
rvm_shell "use rubygems 1.3.7 with default_ruby" do
  ruby_string  node['rvm']['default_ruby']
  code         %{rvm rubygems 1.3.7}
end

# install gems, like:
rvm_gem "nokogiri" do
  ruby_string  node['rvm']['default_ruby']
end

The tricky part is upgrading/downgrading your version of RubyGems after RVM installs and before gems get installed. Hope that helps in the meantime :)

[yfeldblum]

Thanks for the tip.

It would still be cool to have rvm_rubygems be a separate resource, or for rvm_ruby to take a rubygems_version attribute (and up/down-grade rubygems to the specified version, if the version for rubygems is different).

rvm_ruby "ruby-1.9.3-p0" do
  rubygems_version "1.8.11"
end

[fnichol]

I agree and probably the best solution is to provide an rvm_rubygems resource that can also be used by rvm_ruby/rubygems_version. I'm hoping to spend some time with this on the weekend.

[tholschuh]

Any news on this?

[cgriego]

I've made a pull request (#100) that is, I think, the first step in addressing this.

[fnichol]

@cgriego I'm hoping to get a tagged release out and then tackle this one.

[fnichol]

Thanks to @cgriego this is (finally) pulled in. Thanks everyone for helping out on this one.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.