Issue #15980 has been updated by Jared Curtis.
Redhat renames pip to pip-python because the binary clashes with a perl binary of the same name. I would argue that we should default to use the distribution provided binary rather than a 3rd party package. But I don't know how (or if) this sort of decision has been made before in any other modules. Also in your patch you removed the cmd method which was added to allow for OS specific defaults. I think we should keep the cmd method since in the future it would easier to add distribution defaults rather than a global default. ---------------------------------------- Bug #15980: pip provider nonfunctional on redhat-based systems https://projects.puppetlabs.com/issues/15980#change-83433 Author: Eric Shamow Status: Re-opened Priority: Normal Assignee: Jeff McCune Category: provider Target version: 3.1.x Affected Puppet version: 2.6.17 Keywords: pip Branch: https://github.com/puppetlabs/puppet/pull/1348 RHEL installs this binary as pip-python, and the pip provider looks explicitly for a 'pip' binary. Current workaround is a symlink file resource to create the binary, but this should work out of the box. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
