On 2013-28-08 20:58, Ashley Penney wrote:
On Wed, Aug 28, 2013 at 12:05 PM, Ryan Coleman <[email protected] <mailto:[email protected]>> wrote:For simplicity sake, why not keep the language version expression at the module level and not allow one class in a module to use R3 and a second class to use R6. This strikes me as complex without much benefit. The module level should be granular enough IMO. I am worried that even a module level expression is going to lead to problems. Doing support in an environment where the combined set of modules covers 6 language versions is a very real possibility with something like this. While I'm all for modules having a way to express the version of the language they were tested against/support, trying to actually allow differences sounds horrible in actual use. I would be more for the users version of puppet refusing to run modules it doesn't support the language version for and leaving it at that.
Does it alter anything for you if the multi version support is simply "requires a version not older than" and "does not work with versions newer than".
Also, would you like a newer puppet runtime to be able to tell you if language features newer than a given version is being used, or are you fine if that is only detectable by trying to run them on an older version, or check with Geppetto?
- henrik -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
