Feature #7863

Enviroment parameter for Gem package provider type.

Added by Michael Halligan 12 months ago. Updated 4 months ago.

Status:Needs More Information Start date:06/09/2011
Priority:Normal Due date:
Assignee:Michael Halligan % Done:

0%
Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:gem,package
Votes: 0

Description

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.

History

#1
Updated by Jacob Helwig 12 months ago

  • Status changed from Unreviewed to Investigating

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?

#2
Updated by Jacob Helwig 12 months ago

  • Assignee set to Jacob Helwig

#3
Updated by Michael Halligan 11 months ago

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.

#4
Updated by Jacob Helwig 5 months ago

  • Status changed from Investigating to Needs Decision
  • Assignee changed from Jacob Helwig to Nigel Kersten

#5
Updated by Nigel Kersten 4 months ago

  • Status changed from Needs Decision to Needs More Information
  • Assignee changed from Nigel Kersten to Michael Halligan

We need more details on gems that require this and whether they’re still a problem for folks.

Also available in: Atom PDF