Re: tp versions

[Patrice Dumas]

On Thu, Jan 05, 2012 at 09:27:19AM -0800, Karl Berry wrote:
> 
> I agree there's no overwhelming need for the module version numbers to
> be the same as the Texinfo version number, but OTOH, it seems convenient
> and less confusing to make it be so.  At release time.  Or else use
> $Revision$ somehow, if it's possible to strip the dollar signs.  Awfully
> easy to forget to update otherwise.

But we don't want to update unless we do a release of the standalone
perl module (on CPAN presumably).  As for being confusing, it should not
be used anywhere in the texinfo distribution.  I can add a commment in
the code before each $VERSION stating something along

# version of the standalone perl module.  May be different from the
# texinfo version.

Would you want that?

> If standalone perl is ever released, it would surely make sense to
> release it at the same time as a main texinfo release.  Essentially as
> part of doing the texinfo release.

At the same time, but not necessarily each time.  We may want to release
texinfo for the other part of the package, as the info reader, but not
release the perl module at the same time.  In fact I think that we should
release the perl module as rarely as possible.

> I see.  I'd call it Changes-pm then.  And yes, the intro text should be
> clearer.  I can poke at that one of these days, no big deal.

Using Changes matches the tradition on CPAN, so I'd prefer if it stayed this
way.  I can also copy it when doing something that is to be uploaded to CPAN
if you really insist on Changes-pm.

-- 
Pat