I'm not aware of incompatibility issues between minor versions, or even between majors? At least, in data that is created in older versions, the newer ones should be able to read them just fine. The issue would be if we have a newer version writing out data, the older ones wouldn't be able to read it.
Or 64/32 bit issues, but that's a given and we use all 64 bit (or all 32 bit) so we should have no trouble there.
Required versions are based on '>= VERSION', I believe? I know checkconfig.pl operates this way, there's no way of saying 'I want only 2.18'. Even in Perl if you say 'use Foo 2.15;' doesn't that do a >= check?
Anyway, long story short, I don't think it's easily possible (or especially viable) to try to force people to a single version of Storable. As long as you don't mix versions, and you don't downgrade, then it should never be a problem. Maybe we can document the heck out of that.
no subject
I'm not aware of incompatibility issues between minor versions, or even between majors? At least, in data that is created in older versions, the newer ones should be able to read them just fine. The issue would be if we have a newer version writing out data, the older ones wouldn't be able to read it.
Or 64/32 bit issues, but that's a given and we use all 64 bit (or all 32 bit) so we should have no trouble there.
Required versions are based on '>= VERSION', I believe? I know checkconfig.pl operates this way, there's no way of saying 'I want only 2.18'. Even in Perl if you say 'use Foo 2.15;' doesn't that do a >= check?
Anyway, long story short, I don't think it's easily possible (or especially viable) to try to force people to a single version of Storable. As long as you don't mix versions, and you don't downgrade, then it should never be a problem. Maybe we can document the heck out of that.