On 09.03.2014 03:39, Trevor Vaughan wrote:
In theory a composite namevar could be used if you just specify the provider.For instance, on a Red Hat system: package { 'foo': ensure => 'latest' } ==> namevar == foo:yum And package { 'foo': ensure => 'latest', provider => 'gem' } ==> namevar == foo:gem That said, I never could get composite namevars to work this way. I always had to have a unique name which ended up in something silly like package { 'foo_rpm':} or package { 'foo_gem':} which, while it should work, is absolutely horrible to read.
That was my understanding how composite namevars should have worked from the beginning. Sadly, this seems "too complex" or "not useful enough" to be actually implemented. It would even help for multi-arch and multi-versions installations: "foo:1.0:i386:yum" vs "foo:2.0:amd64:yum".
Regards, David -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/531C426F.1000903%40dasz.at. For more options, visit https://groups.google.com/d/optout.
