On Tue, Jun 11, 2013 at 7:13 PM, Rags <[email protected]> wrote: > Puppet manifests today don't specify the version of DSL they are writing to, > afaik. This will likely lead to the classic versioning problem. Imagine a > new language construct gets added and not all Puppet versions can support > this language construct. Without having a way to know the DSL version of a > Puppet manifest, this mismatch can only be detected at runtime in an adhoc > manner.
Can you give an example where this would be a problem? Just about every language with versions is in the same situation, and none that I can think of annotate the source with the language version. Puppet has done some interesting things with "from __future__ import..", but to my mind that works the other way around, and is functionally equivalent to the "future" configuration option in puppet. Dustin -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
