Re: [PATCH] fix dist.sh tar-ball name.

On 10 Mar 2003, Karl Fogel wrote:

> Michael Price <mprice@atl.lmco.com> writes:
> > Because then you get:
> >
> > $ svn --version
> > svn, version 0.19.0 (0.19)
> >
> > rather than:
> >
> > $ svn --version
> > svn, version 0.19.0 (r5240)
> >
> > I thought the rXXXX stuff was useful in the --version text, it just
> > makes for a silly tar-ball name.
>
> Ah, I see. I guess dist.sh will need to explain this better... :-)

Pardon my ignorance beeing a newcomer and all, but why is the repository
version number interesting at all? You need to know what subdir you are
referring to anyway, and if you have say /tags/release-0.19, then that is
all you need to know, isn't it? All newer repository versions should
contain the same version of the /tags/release-0.19 tree, or else it is not
working as a tag. I understand that you (technically) *can* update
/tags/release-0.19, but policy should be to to forbid such actions,
shouldn't it?

Or are you adding the repo version to safe-guard against accidental
modification of the tag?

In essence, why not simply the following if build from a tag,

    $ svn --version
    svn, version 0.19.0

and possibly

    $ svn --version
    svn, version r5240-trunk

if it's built from the trunk.

/Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 10 23:59:48 2003