I'm not 100% sure if this works as you would expect in your manifests,
but I've used something like this to build a redmine class:
class ruby-gems::install {
package { 'ruby1.9.1': ensure => present }
}
class bundler::install {
Package {
require => Class [ruby-gems::install],
before => Class [ruby-gems::install],
}
package { 'bundler':
ensure => present,
provider => gem
}
}
Would be interested in how you ended up resolving this though ...
On Nov 25, 2:21 pm, Martin Alfke <tux...@gmail.com> wrote:
> Hi,
>
> we want to install the ruby-gem package on a Debian system using puppet.
> package { 'ruby1.9.1': ensure => present }
>
> In another manifest we want to use the gem provider to install a ruby gem.
> package { 'bundler': ensure => present, provider => gem }
>
> On the first run the puppet agent run checks for a functional gem binary on
> the system.
> It will not find gem installed and claims gem provider to be unusable.
> On the second run puppet now finds the gem provider.
>
> Is there any known method which will allow us to use gem provider also on the
> first puppet run?
>
> Note1: Using stages will not solve this.
> Note2: We would not like to execute a puppet restart after ruby1.9.1 package
> installation.
>
> Thank you,
>
> Kind regards,
>
> Martin
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
