Re: Take care with version numbers (eg DBD::Pg)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


>> I can't see a case where using both forms would ever be desired.
>
> In my META.yml, I'll use three-digit notation for modules that use it 
> (DBD::Pg) and decimal for those that don't (DBI).

Right, I didn't mean to imply you can't mix and match across modules.

> It might be useful for the version validation code to complain if I 
> specify decimal and the module uses three-digit (or vice versa).

Could be a lot of work, yes, but it would certainly catch things like 
the existing RWDE problem (as would my proposal by itself).

> But then that would screw things up for modules that unfortunately 
> changed their versioning algorithm. I would no longer be able to 
> require DBD::Pg 1.49, for example, even thought that's perfectly valid.

Good point, but hopefully such changes are a very rare and momentous event 
(as was the case with DBD::Pg). Version 1.49 (the last of the two dot 
versions for those playing at home) is *severely* deprecated. One of the 
reasons DBD::Pg jumped to 2.0.0 was to prevent any version comparison 
confusion, as even Perl's wacky versioning tools cannot deny that 2 > 1. :)

- -- 
Greg Sabino Mullane [email protected]
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201007081340
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkw2DsMACgkQvJuQZxSWSsjeLACgsakZH/iVhwltaCqXOMOmcF8e
ZBkAnjJlhWBgf0jWMJiRsPJDUkXWbxF2
=MhsI
-----END PGP SIGNATURE-----