Issue #7863 has been updated by Michael Halligan.
Jacob Helwig wrote: > I don't think I've ever seen (or even heard of) that behavior with a gem > before. Do you have an example of a gem & system combination that requires > setting an environment variable to install it? Jacob, most commonly I need to do this when I'm coming in to puppetize a site with a legacy/older rails stack, to shoehorn gems into place. I also find myself having to do this to force architecture types. For example I had to do this to force the ARCHFLAGS environment variable to i386 in a small ec2 image for the mysql 0.8.1 gem. ---------------------------------------- Feature #7863: Enviroment parameter for Gem package provider type. https://projects.puppetlabs.com/issues/7863 Author: Michael Halligan Status: Investigating Priority: Normal Assignee: Jacob Helwig Category: Target version: Affected Puppet version: Keywords: gem,package Branch: In different systems a number of gems often require you to set an environment variable before installation. It seems that people currently handle this with an Exec, but an environment parameter might be cleaner. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
