From this example:
package { 'foo':
ensure => '1.0.0',
}
package { 'foo':
ensure => '1.0.1',
}
package { 'foo':
ensure => 'latest',
}
Which one wins? Since resources can be evaluated and applied in any
order (barring dependencies), you could end up in a situation where a
package
I've encountered the problem where 2 modules declare the identical package.
I wonder why package { .. } doesn't check if the package is already
declared, and the redundant declaration can be ignored.
Will it be a nice improvement? If not, why not?
Thank you,
Tanin
--
You received this messag
