Using puppet 3.0.1 I ran into an odd scoping problem - I've got a class
called 'lettuce' in a module named testtools, like this:
class testtools::lettuce {
require pip
Package {
provider => pip,
}
package {
"lettuce":
ensure => installed;
"lettuce-webdriver":
ensure => installed;
}
}
Then I've got a class 'pip' in a module named 'pip' (the class is in the
module's init.pp):
class pip {
package { "python-pip":
ensure => installed,
}
}
When I included testtools::lettuce on a node, it tried to install the
'python-pip' package, *using* pip, i.e. trying to run /usr/bin/pip install
-q python-pip
The python-pip package is meant to be using the default 'apt' provider, but
it looks like the Package { provider => pip } from a completely different
module is overriding its default. I thought Puppet 3's removal of dynamic
scoping wouldn't allow this?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/wieRwBLolP4J.
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-users?hl=en.
