|more useful options|
Versioning modules in a packageby legLess (Hermit)
|on Oct 04, 2004 at 18:17 UTC||Need Help??|
legLess has asked for the
wisdom of the Perl Monks concerning the following question:
I have questions about how to version modules in a package. They boil down to: if and how should I synchronize internal $VERSIONs amongst the modules and with the package version. Specific questions (with my answers at the end):
Given package Foo, containing Foo.pm, Foo/Bar.pm, Foo/Baz.pm:
It seems to me that $Foo::VERSION is the effective version of the entire package, and should only be changed for new package versions. $Foo::Bar::VERSION and $Foo::Baz::VERSION should be changed as their internal changes demand.
This doesn't account for minor changes to Foo.pm itself. If I'm not ready to make a new package version, these changes would go unversioned, except by Subversion's $Id$ string. The same is true of the sum-modules: minor versions are tracked by Subversion, major ones by $VERSION.
Is this common practice? Any thoughts?