On 02/12/2014 12:18 PM, Jason Antman wrote:
>
> - explicit version specification is a very good thing, if version
> comparison is reliable and in step with the underlying package system.
> I'd love to be able to specify ">= 1.2.3"
I'm torn. The sync action would be "update to latest", no? So I'm not
sure the overhead is justified, seeing as puppet can do that without
problems already.
What the >$VERSION scheme introduces is behavioral ambiguity, I feel,
and while it may seem neat to be able and jot such information down in a
module, again, the benefit is limited, seeing as such matchers won't stack.
Btw., from PUP-1519
package { 'foo': ensure=>'<4.0' }
would act as 'installed' if version is <4.0 but would produce an error
otherwise.
This doesn't fit with puppet's MO at all. Out-of-sync properties should
really have a way to get in sync, imho, and provoking resource failures
to notify the user of manual actions required just feels very wrong.
Regards,
Felix
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/52FB5F10.8080204%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.
