in reply to CPAN: Module version versus kit version

Generally I (as an author) ensure that all modules within a dist (which you are calling a "kit" here) have the same version number and that version matches the dist. That way there is no ambiguity. Occasionally this means that more than one "version" of any given module may be identical, except for the version number. I'm happy with that anomaly as the price to pay for consistency.

It is also one of the kwalitee measures so I take that as something to aspire to. Other opinions are valid too, of course.


🦛

  • Comment on Re: CPAN: Module version versus kit version

Replies are listed 'Best First'.
Re^2: CPAN: Module version versus kit version
by sciurius (Beadle) on Dec 06, 2024 at 12:26 UTC

    Ok, bottom line seems to be to update the module version even if the module itself did not change.

    Thanks for the feedback.