Feature #3708

Allow alternate 'gem' command in gem provider

Added by Mark Plaksin almost 2 years ago. Updated 5 months ago.

Status:Accepted Start date:05/03/2010
Priority:Low Due date:
Assignee:- % Done:

0%
Category:package
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 2

Description

This would let us, for example, install gems into our RubyEE install.

I haven’t looked but it’s possible this same sort of thing applies to other package providers.

History

#1
Updated by James Turnbull almost 2 years ago

  • Category set to package
  • Status changed from Unreviewed to Needs More Information

By alternative gem command – do you mean options to the command?

#2
Updated by Mark Plaksin almost 2 years ago

I mean allow us to use, for example, /usr/local/ruby-ee/bin/gem for certain gems instead of /usr/bin/gem.

#3
Updated by James Turnbull over 1 year ago

  • Status changed from Needs More Information to Needs Decision

Not sure the best way to do this because gem strikes me as the only provider likely to need this?

#4
Updated by James Turnbull about 1 year ago

  • Assignee set to Nigel Kersten

#5
Updated by Nigel Kersten about 1 year ago

This is a bit problematic due to how we confine providers.

Can you work around the issue with a symlink instead?

#6
Updated by Mark Plaksin about 1 year ago

Sure a symlink could work but it doesn’t let you manage gems for multiple ruby installs. It’s not the most common case but there are times when we’d like to do that. One set of gems for the OS-provided Ruby and one for ruby-ee.

#7
Updated by Nigel Kersten about 1 year ago

I misremembered how the gem provider is confined, it turns out that it’s not looking for a fully-qualified path to ‘gem’ at all.

I think I’d like to see us solve this in a more general way. I wonder if we could effectively have a “path” metaparameter that let you specify the PATH environment variable for any resource, and then you could use this to achieve this goal.

#8
Updated by Robin Powell 10 months ago

Just a bump to say that I would like this as well; I’m on a system with jruby and normal ruby, and they have different sets of gems they need, and it’s not avoidable.

-Robin

#9
Updated by Nigel Kersten 5 months ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)
  • Priority changed from Normal to Low

Also available in: Atom PDF