Re: [Puppet Users] package conflict resolution method:

Jason Antman
Fri, 01 Nov 2013 21:19:26 -0000

Tom,

I''ve actually been working with similar issues lately (and am in the
process of working on a virtualenv module).

I have a python module that includes classes for the common dependencies
(i.e. "require python::pyyaml") and have been pretty happy with that
pattern so far, but if you want, I believe the stdlib ensure_packages()
can also do this.

-jantman

On 11/01/2013 05:03 PM, Tom Noonan wrote:
> Hello, list:
> 	I have two puppet modules that are unrelated to each other, but
> both have (unrelated) Python scripts that parse YAML.  As such, both
> have a block like the following in their manifests for the PyYAML script
> dependency:
>
>       package { ''PyYAML'':
>         ensure  => installed,
>       }
>
> 	If I try and include both modules on the same server this
> causes an obvious conflict as the PyYAML package is now defined in two
> different package{} blocks.
> 	Can the list please advise on what best practice is in this
> case?  I''d prefer not to create a whole other module just to do a
class
> dependency for PyYAML, but if that is best practice so be it.  Please
> let me know if I''m overlooking any other solutions.  Thanks!
>
> --Tom N.
>
>
>

--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit