2009/4/20 Eric Wilhelm <[email protected]>: > I'm fine with the current behavior, but the spec needs to be clarified. > What's the canonical handling? Is it 'version->new($meta->{version})'? > > http://module-build.sourceforge.net/META-spec-current.html#version_specifications
Definitions of file formats based solely on the behaviour of some program external to the specification is generally not a good idea... As a fallback position, the spec must at minimum define the version of version.pm that is considered authorative. > If META.yml is used for Perl modules, it is reasonable to say that > versions must be stringified and compared ala version.pm. If META.yml > is for something beyond Perl modules then I'm in over my pay grade. That's a safe call. Any kind of future multi-language equivalent to META.yml will be a new file format, most likely in XML or RDF or similar, and we'll be transforming META.yml into it instead of using META.yml natively. > I can't see numify becoming the spec without causing trouble and I don't > see the benefit. Mostly for me, it allows the specification to be complete (in the sense everything is defined in the spec). Specifying version.pm in the META.yml specification is a lot like the OOXML 'parse-like-word-95' properties. Adam K
