On Mon, Mar 3, 2008 at 12:35 PM, Andy Lester <[EMAIL PROTECTED]> wrote:
>
> On Mar 3, 2008, at 2:34 PM, Bill Ward wrote:
>
> > Then don't try to have just one standard. Perl is smart enough to
> > understand multiple standards. Just document what those are and
> > provide some means of descri
On Mar 3, 2008, at 2:34 PM, Bill Ward wrote:
Then don't try to have just one standard. Perl is smart enough to
understand multiple standards. Just document what those are and
provide some means of describing how they map to one another, and list
the alternatives clearly on the documentation f
On Mon, Mar 3, 2008 at 11:22 AM, Andy Lester <[EMAIL PROTECTED]> wrote:
> On Mar 3, 2008, at 1:20 PM, Eric Wilhelm wrote:
> >> Are there any compelling reasons to keep allowing any type of version
> >> numbers?
>
> I suspect that the amount of time saved by any benefits from
> standardized version
On Mon, Mar 3, 2008 at 2:22 PM, Andy Lester <[EMAIL PROTECTED]> wrote:
> I suspect that the amount of time saved by any benefits from
> standardized version numbers will be dwarfed by the amount of time
> spent arguing over what the standard should be.
We can kill two birds with one stone by argui
On Mar 3, 2008, at 1:20 PM, Eric Wilhelm wrote:
Are there any compelling reasons to keep allowing any type of version
numbers?
I suspect that the amount of time saved by any benefits from
standardized version numbers will be dwarfed by the amount of time
spent arguing over what the stand
# from Gabor Szabo
# on Monday 03 March 2008 11:05:
>As far as I can tell there is already an almost universally accepted
> format of \d+\.\d\d for released versions and \d+\.\d\d_\d\d for
> development versions.
>
>Are there any compelling reasons to keep allowing any type of version
> numbers?
Hi,
I know Perl is all about diversity but I wonder if requiring a uniform
way of providing version numbers of modules on CPAN would be too much
of restriction on the freedom of module authors?
I think it would make life easier for tool authors (PAUSE/CPAN.pm/CPANPLUS etc)
and downstream distro p