On Feb 24, 5:52 am, jcbollinger <john.bollin...@stjude.org> wrote: > On Feb 23, 4:57 pm, AlanLaird<a...@laird.net> wrote: > > > Any suggestions on the right way to do this? > > If neither of the things you already tried works, then perhaps you > should fall back to "don't worry about it." If you install software > only from packages, then, since you're usign the yum provider, > installing any other package that needs libstdc++.i386 will cause > libstdc++.i386 to be installed too. And installing only from packages > is an excellent practice, even if it means you sometimes have to roll > your own packages and maintain a local package repository (neither is > hard). > > Personally, I am inclined to lean heavily on my package manager. I > think it's more robust and maintainable to have Puppet manage only my > direct package requirements.
This is a third-party package with poorly constructed depends in a mixed 32 and 64 bit environment as I support moving from Centos5 to Centos6. Repackaging the vendor package is easy but it would need to be done at each release. I've solved the problem of the day by installing the needed libstdc+ +34-3.4.0-1.i386 specifically but it's a clunky way to deal with this issue. I would love to find a crafty puppet way to do this. Alan -- 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.
