comment on

It's easy enough to force a version number to change if it needs to.

I think you're right about the dubious value of using revision numbers as version numbers, but I'm confident these numbers aren't used for anything. I thought they might be useful at some point, but I never found that point, and the code in question isn't used by anyone else.

So this may be my big chance to get rid of something that's not needed. Still, I'm curious, since this seems like something that ought not to require the amount of effort that it does.

Thanks for your thoughts.

In reply to Re^2: Best Practice for automatic version numbers? (no, how) by kyle
in thread Best Practice for automatic version numbers? by kyle

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks