![]() |
|
Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Re: CPAN: Module version versus kit versionby NERDVANA (Priest) |
on Dec 06, 2024 at 01:00 UTC ( [id://11163050]=note: print w/replies, xml ) | Need Help?? |
If you don't change the module version, it breaks things for various people.
One time I had a goal of shipping a collection of different modules in the same dist where the version of the module was the last change to *its* API. People complained that the versions were different from the package. Another problem I've seen is when you change the number of digits in the dist, it breaks the mapping from CPAN version to Linux distro version, because the distros are taking our packages and giving them numbers like Foo-1.10.0-debian-5. Other distros choose Foo-1.100.0 by converting the full perl version as per Version.pm. As soon as you make the version number "1.10.1" all the distro maintainers have to manually get involved to decide what to do about it. Anyway, it's not ideal, but if you want to cause the least problems for the most people, always use the same version for everything in the dist and never change the number of digits. Document the fact that nothing actually changed in the Changes file.
In Section
Seekers of Perl Wisdom
|
|