Re^2: $VERSION in module files

Replies are listed 'Best First'.
Re^3: $VERSION in module files by tobyink (Canon) on Mar 26, 2020 at 16:04 UTC
I usually use perl-reversion for changing all the version numbers for every module in a distribution. toby döt ink	[reply]
Re^4: $VERSION in module files by bliako (Monsignor) on Mar 27, 2020 at 12:55 UTC
`perl-reversion` works for me. It changed both `our $VERSION` and POD versions. Worrying thing is that it scanned bash files too... (just tried inserting a `VERSION=0.21` in a bash script and `perl-reversion` bumped that version too. Definetely good to know but perhaps a bit dangerous.)	[reply] [d/l] [select]
Re^5: $VERSION in module files by tobyink (Canon) on Mar 28, 2020 at 14:49 UTC
You can give it a list of files and directories to limit what it scans. Hopefully if you do `perl-reversion --bump bin/*.pl lib` it'll only be finding Perl files. toby döt ink	[reply] [d/l]
Re^3: $VERSION in module files by hippo (Bishop) on Mar 26, 2020 at 11:14 UTC
Not necessarily. If you maintain a version number for the dist which applies also to all the modules then you can pick one master module which all the others use and have them set their versions from that one. eg. `package Foo; our $VERSION = '1.01'; # ... package Foo::Bar; use Foo; our $VERSION = $Foo::VERSION;` [download] I never bother specifying version numbers in POD so you're on your own there. :-) Doubtless there's a way in Dist::Zilla but then you'd have `$problems++`	[reply] [d/l] [select]
Re^4: $VERSION in module files by Haarg (Priest) on Mar 26, 2020 at 12:55 UTC
If you specify the module version like this, it won't be picked up by tools like ExtUtils::MakeMaker, and won't be properly indexed on CPAN by PAUSE. The version needs to be specified by a single line, and won't be able to load modules from the current distribution.	[reply]
Re^4: $VERSION in module files by haukex (Archbishop) on Mar 26, 2020 at 12:25 UTC
`package Foo; our $VERSION = '1.01'; # ... package Foo::Bar; use Foo; our $VERSION = $Foo::VERSION;` [download] If that's in a single file that may work, I'm not sure, however, I suspect at least some of the tools that rely on a static parse won't be able to handle that.	[reply] [d/l]
Re^5: $VERSION in module files by hippo (Bishop) on Mar 26, 2020 at 13:34 UTC
For the static parse I rely on the "provides" list in the metadata. For the above example the Makefile.PL includes something like this: `my $release = '1.01'; my %MF = ( META_MERGE => { 'meta-spec' => { version => 2 }, provides => { 'Foo' => { file => 'lib/Foo.pm', version => $release }, 'Foo::Bar' => { file => 'lib/Foo/Bar.pm', version => $release }, }, }, # ... }; WriteMakefile (%MF);` [download] So the version is specified explicitly twice: once in the Makefile.PL and once in the master module. If there's a reliable way to specify it explicitly only once that would be good to know.	[reply] [d/l]
Re^6: $VERSION in module files by Haarg (Priest) on Mar 27, 2020 at 10:35 UTC
Re^7: $VERSION in module files by hippo (Bishop) on Mar 27, 2020 at 11:00 UTC
Some notes below your chosen depth have not been shown here
Re^4: $VERSION in module files by Anonymous Monk on Mar 26, 2020 at 21:23 UTC
Not necessarily. If you maintain a version number for the dist which applies also to all the modules then you can pick one master module which all the others use and have them set their versions from that one. eg. inheriting a version number is like inheriting your fathers age/birthdate yeah my wife just gave birth to a beautiful baby, 9lbs, 32 years old	[reply] [d/l]
Re^5: $VERSION in module files by soonix (Canon) on Mar 27, 2020 at 04:23 UTC
Yes and no. It can also be like having different birthdays for your limbs. It might make sense for a peg leg, but mostly unnecessary. Depends on how interdependent the modules are.	[reply]
Re^6: $VERSION in module files by Anonymous Monk on Mar 27, 2020 at 07:52 UTC
Re^7: $VERSION in module files by soonix (Canon) on Mar 27, 2020 at 08:12 UTC
Some notes below your chosen depth have not been shown here
Re^3: $VERSION in module files by pryrt (Abbot) on Mar 26, 2020 at 13:15 UTC
In Win32::Mechanize::NotepadPlusPlus, I added a rule in my Makefile.PL postamble, so that `make populateversion` will take the VERSION that the Makefile sees (which it grabs from the "primary" module in the dist, thanks to `$mm_args{VERSION_FROM}` ), and uses perl to do an in-place edit of the `our $VERSION =...` from the related modules. `# auto-populate the VERSION in the submodules from $(VERSION), which c +omes from main module populateversion :: lib/Win32/Mechanize/NotepadPlusPlus.pm $(NOECHO) $(ECHO) want to auto-populate VERSION in all sub-modules +: $(VERSION) $(PERL) -pi -e "s/^(\sour\s+.VERSION\s=).?;.?$$/\1 '$(VERSION) +'; # auto-populated from W::M::NPP/" lib/Win32/Mechanize/NotepadPlusP +lus/Notepad.pm lib/Win32/Mechanize/NotepadPlusPlus/Editor.pm` [download] So I just have to change the version in one master location, and then `make populateversion` (or, since I have other rules that depend on that rule, run one of those other rules for doing other documentation updates) to get the version in sync across the modules.	[reply] [d/l] [select]


There's more than one way to do things
	PerlMonks