----- Original Message ----- > Point taken. > > Back to the RPM issue. For those of us that do not use a standard > system-provided ruby installation, such as Enterprise Ruby, how can > we > mitigate the installation so that it works? > > As I mentioned earlier, I tried this with --nodeps and the ruby > script > could not "require" the mcollective bit. Given that I just verified > that /usr/bin/env is working properly, I think we can safely > eliminate > that. > > What would be the best approach to get this working properly? > Enterprise Puppet also uses Enterprise Ruby, so I wonder how they've > handled it.
Did you rebuild the RPMs like I said yesterday with the ruby in your path correctly setup? Then the resulting RPMs will install into your enterprise directory. I also showed you how to install rpms bypassing the dependency checks and also told you that you could just edit the requirements from the spec files. -- R.I.Pienaar -- 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.
