On Sun, Apr 19, 2009 at 6:41 AM, John Peacock <[email protected]> wrote: > However, using $version->stringify() instead would be better than having > META.yml contain an object dump for $VERSION. The version.pm object is > guaranteed to stringify to the same form as was original present in the source > file, which is the _only_ way to preserve the author's intention. Since most > of > the toolchain treats $VERSION as an atomic THING, and the few places which try > to compare one $VERSION to another are already wired up with version.pm, this > will work as any sane person would expect it to...
For clarity -- since there's been a lot of emails on this topic already -- the issue isn't version.pm object dumps. That was a bug that was fixed a while ago in most/all of the META.yml generators. The discussion started with a complaint that M::B shouldn't put "v1.2.3" (as a string) in META.yml but should always numify it to 1.002003 instead. The original reason for the complaint turns out to be that Test::YAML::Meta wouldn't parse "v1.2.3", but the debate has spun out to two broader questions: * How tightly should the distribution "version" in META.yml correspond to the unique name of a distribution file on CPAN and what are the implications if it doesn't? * How should non-perl things (like Debian packagers) deal with multitude of version formats and would it be better to establish a simple, mechanistic standard along the lines of what numify does? -- David
