Because there's no way to know which distribution version you have
after it is installed if you do it that way.
A secondary reason would be that it is so common to match the
distribution version and the module version that many tools are
written with that assumption built in.
By matching the conventions that are most commonly in use, you are
more likely to be compatible with the tools in use.
Adam K
2009/6/16 mrouchal@arcor.de via RT <bug-Pod-Parser@rt.cpan.org>:
Show quoted text> Queue: Pod-Parser
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=46695 >
>
> Is that a problem? The version of the distribution is defined in
> Makefile.PL - and that is updated with each release, e.g. when
> only Checker.pm gets an update (and thus a new version). The
> only exception: if Parser.pm gets an update, I update the version
> to the (new) distro version. But why should I update
> $Pod::Parser::VERSION if the file did not change?
>
> -Marek
>
> -----Ursprüngliche Nachricht-----
> Von: Dave Mitchell via RT [mailto:bug-Pod-Parser@rt.cpan.org]
> Gesendet: Samstag, 6. Juni 2009 00:38
> An: undisclosed-recipients:
> Betreff: [rt.cpan.org #46695]
>
> Fri Jun 05 18:38:03 2009: Request 46695 was acted upon.
> Transaction: Ticket created by davem@iabyn.com
> Queue: Pod-Parser
> Subject: (No subject given)
> Broken in: 1.38
> Severity: Normal
> Owner: Nobody
> Requestors: davem@iabyn.com
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=46695 >
>
>
> Pod/Parser.pm in the 1.38 Pod-Parser distribution still identifies
> itself as version 1.37 !
>
>
>
RT for rt.cpan.org