John M. Gamble wrote:
> On Sat, March 16, 2013 7:43 am, Linda W wrote:
>
>> Different Q:
>>
>> Is there "easy" way to have the version number in the pod be taken from
>> it's
>> definition in the code rather than having it be static text that needs to
>> be updated? Seems an odd thing not to be 'automatic'...
>>
>>
>
> There was a discussion on this back in January/February
> (http://www.nntp.perl.org/group/perl.module-authors/2013/01/msg9894.html).
----
It is related, but a separate category -- as the pod and the code
are in the same file -- but I have to update the version in two places
-- the $Version for the version that cpan gets, and the text string for
the version that is in the pod. I tried something simple like putting
$Version where it looks for a version -- all that got me was
Version: $VERSION
---
i.e. no symbolic or variable substitution in the perl-pod processors.
Having the version 'bump' on change is a different issue. I check in
a new version on my RCS... but I wouldn't want to use it's version as the
release version, as I use RCS to somewhat 'checkpoint' work when things are
working or I finish something.
With the discussion I read at the link above, they were more concerned about
changing the version number in one place for multiple files. Related
issue, but
likely different. Certainly we could all play games with specialized
perl scripts that search for the version in a common location
and patches one or more source files in one or more locations/source
file, but
it that seems a bit inelegant. Though if it bothered me
enough...inelegance is
fine... ;-)
