Issue #17030 has been updated by eric sorenson. Status changed from Unreviewed to Needs More Information Assignee set to Bradley Kreider
Generally the way to influence the commands that the provider system uses is to adjust puppets $PATH before it starts up, since internally it just tries to execute the command without a fully-qualified pathname in order to account for '/usr/bin' vs '/usr/local/bin' style variances in Unix flavours. I could see the call for adding this as a parameter to the package resources though, especially given #15980 and since you could use a higher level default and override it if needed. Does the $PATH workaround suffice for you? Care to take a stab at a patch? ---------------------------------------- Bug #17030: pip provider should handle multiple pips/pythons https://projects.puppetlabs.com/issues/17030#change-77649 Author: Bradley Kreider Status: Needs More Information Priority: Normal Assignee: Bradley Kreider Category: provider Target version: Affected Puppet version: 2.6.17 Keywords: Branch: The Pip provider should provide a way to specify the path to pip. This would allow people to manage multiple python installs, by point to the one they want to install into. In RHEL, this makes it easy to have a non-system python installed somewhere (ie: 2.7 or 3.x) and let puppet manage the python packages. This is related to bug #15980. (related in the way that if you could provide the path to the pip binary, 15980 would have a workaround). -- 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.
