On Thu, Jan 27, 2011 at 14:47, Nick Lewis <[email protected]> wrote: > On Thu, Jan 27, 2011 at 2:19 PM, Kenn Hussey <[email protected]> wrote: >> >> What are the allowable constraints on module dependency version >> requirements? So far, I've only ever seen "greater than or equal" >> used, e.g., '>= 1.2.3'. It seems that other qualifiers ought to be >> allowed/supported, e.g., "compatible", "equivalent", "perfect", etc.. > > A brief look into the code indicates that the available matchers in the > Forge are ==, >, <, >=, and <=. Comparison defers to Versionomy, so I'm not > sure exactly what is considered to match. Playing around with Versionomy, > the matching seems intuitive enough. 1.2.3.a == 1.2.3a > 1.2.3 > 1.2 > 1. > Are there any comparisons that you were thinking that aren't possible with > those?
Given the specific set of version selectors, I strongly suspect that Kenn is using the Ruby GEM version specification language as his template: http://docs.rubygems.org/read/chapter/16 That does allow for specification of some "compatibility" version requirements that make sense *if* everyone is following the same version numbering rules. (I doubt Debian could use them effectively, for example, because the set of practices in use across all projects is too broad.) Now, I don't honestly know if there is much value to puppet and the forge in supporting gem-like version requests, but at least we can talk with one common language. :) Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <[email protected]> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
