* Johan Vromans [EMAIL PROTECTED] [2008-07-09 17:10]:
What are the alternatives?
You probably want to use git-describe in your build script.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Jim Schneider [EMAIL PROTECTED] writes:
This should be handled by your release building tool (a feature that
seems an obvious no-brainer, once it's been pointed out that it's
missing).
Yes, and no.
In general, a package has a version associated. For this version
number the release building
Johan Vromans wrote:
But for all the individual modules that are part of a package? Their
version numbers should only increase when something changed, i.e., at
commit time. Not at release time.
Let me speak against this. I find non-uniform version numbers a pain. Version
123 of
Hello,
I prefer the individual package versioning too.
What I have experienced over time is that single packages sometimes
are separated out into separate distributions and due to the nature of
the Perl package name spacing, a version number should be at least
present.
Nothing speaks
On Fri, Jul 11, 2008 at 10:57 AM, Johan Vromans [EMAIL PROTECTED] wrote:
But for all the individual modules that are part of a package? Their
version numbers should only increase when something changed, i.e., at
commit time. Not at release time. A task very neatly handled by CVS.
And for which
On Wed, Jul 9, 2008 at 8:09 AM, Johan Vromans [EMAIL PROTECTED] wrote:
The CPAN indexer requires perl modules (and sub-modules) to have a
non-descending VERSION number. RCS/CVS $Revision$ has been invaluable
for that.
Not really. If you use RCS/CVS numbers, then you have several problems:
1.
with Nextel Direct Connect
-Original Message-
From: Bill Ward [EMAIL PROTECTED]
Date: Fri, 11 Jul 2008 14:58:06
To: Johan Vromans[EMAIL PROTECTED]
Cc: module-authors@perl.org
Subject: Re: VERSION and VCS
On Wed, Jul 9, 2008 at 8:09 AM, Johan Vromans [EMAIL PROTECTED] wrote:
The CPAN indexer
Bill Ward wrote:
Because of these issues I feel it's best to just update the version
numbers when a release is made. You might as well do this by hand,
since you need to update the README, CHANGES, etc. files at the same
time.
Well, not exactly by hand, but initiated by hand, yes.
The CPAN indexer requires perl modules (and sub-modules) to have a
non-descending VERSION number. RCS/CVS $Revision$ has been invaluable
for that.
Now more and more development is migrating towards VCS that do not
have such a feature (git, svn, hg, ...).
What are the alternatives?
Manually
# from Johan Vromans
# on Wednesday 09 July 2008 08:09:
Now more and more development is migrating towards VCS that do not
have such a feature (git, svn, hg, ...).
What are the alternatives?
Just use the integer time()?
Manually updating the version numbers of changed modules before a
release
10 matches
Mail list logo
