I'd be very wary of using the SVN repository revision as your package's version number. You're conflating a particular state of your repository with a particular public release. Not as automagic, but it might be better to manually retain a more traditional major.minor.patch variable and use svn cp to create a tag in your repository.

Update: Again, this is IMHO. I haven't maintained anything publicly released with SVN (haven't moved my piddling couple of CPAN modules over to SVN yet), so don't take this as gospel. I'd be interested in hearing more from people who are using SVN in live practice.

--
We're looking for people in ATL

In reply to Re: "Subversion" revision numbers as 0.01_blah by Fletch
in thread "Subversion" revision numbers as 0.01_blah by rvosa

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.