Closed matellis closed 13 years ago
I haven't tried this yet, but would this work:
rvm_gem {
'bundler192':
name => 'bundler',
ruby_version => 'ruby-1.9.2-p180',
ensure => '1.0.13',
require => Rvm_system_ruby['ruby-1.9.2-p180'];
}
rvm_gem {
'bundler187':
name => 'bundler',
ruby_version => 'ruby-1.8.7-p334',
ensure => '1.0.13',
require => Rvm_system_ruby['ruby-1.8.7-p334'];
}
That gave an error on the second stanza saying it couldn't set the alias 'bundler' as it was already defined.
However this does work:
rvm_gem {
'bundler':
ruby_version => 'ruby-1.9.2-p180',
ensure => '1.0.13',
require => Rvm_system_ruby['ruby-1.9.2-p180'];
}
# TODO: This is a hack, see https://github.com/blt04/puppet-rvm/issues/6
rvm_gem {
'bundler187':
name => 'bundler',
ruby_version => 'ruby-1.8.7-p334',
ensure => '1.0.13',
require => Rvm_system_ruby['ruby-1.8.7-p334'];
}
Feels a bit hacky. Hopefully all our third party software like Puppet will be Ruby 1.9.2. compliant by the time we want to deploy 1.9.3.
Thanks for this bug report. 381a747 adds support for my first suggested syntax. You shouldn't have to use your hack, though it will still work.
That was fast! Thanks a lot.
If you install two versions of Ruby (say 1.8.7 and 1.9.2) and try to install bundler for each of them you get an error. Specifically:
Won't work. If you change the name for them to be something like
bundler187
andbundler192
then it can't find the right gem (of course).Will this need a patch or am I missing something here?