On 04/01/2014 01:44 AM, Trevor Vaughan wrote: > I have to say that I like 'hold' better than 'held' based on the way I > would actually read this.
Right, and I don't agree about John's point about property names. There are counter-examples that work very well like service/enable, file/purge, file/recurse etc. The inconsistency with yumrepo/enabled is unfortunate. When I read those, I think 'imperative', which really is what the manifest represents. Ensure this! Hold that! :-) On 04/01/2014 03:20 PM, Trevor Vaughan wrote: > I like hold and purge as separate parameters for readability (which > translates to being easier to parse with external scripts if necessary). > > Trevor > > > On Tue, Apr 1, 2014 at 9:09 AM, Daniele Sluijters > <[email protected] <mailto:[email protected]>> wrote: > > If we go down this road, how does 'purged' fit in. Should we have > purge => true, or ensure => 'purged'? Hmm, no. Seeing as 'purged' in this context is an installation state competing with installed or removed, it should stay in the ensure property, which is what manages installation states. E.g., this makes little sense: package { 'foo': ensure => 'installed', purge => true } Cheers, 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/533ABE41.1080809%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
