[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: new substitution keyword for global repository revision

From: Branko Čibej <brane_at_xbc.nu>
Date: Sun, 27 Dec 2009 18:11:05 +0100

Christian Schoenebeck wrote:
> On Saturday 26 December 2009 18:08:15 Branko Čibej wrote:
>
>> Every couple of years someone comes up with a proposal like this, and it
>> usually ends with a client-side hooks idea. Beh. Subversion is a version
>> control system, not a build systam. If you want "current global
>> revision" to label your builds, use Hudson or Buildbot or the dozon
>> other build automation systems that are integrated with Subversion.
>>
>
> I don't see a mandatory connection to a build system here. There could also be
> static HTML content be managed by the VCS, which doesn't require any build
> facility at all. You can deny it as much as you want, but the frequency of
> people coming up with this feature request shows that a lot of people see this
> obligation of version number substitution on VCS side.
>

I think these requests are only the result of there actually being a
global revision number. If Subversion did not have that, or did not
expose it to the user, no-one would ever think of requesting such a
feature. Clearly users of other version control systems solve the same
problems differently. Maybe they use tags or some other labelling mechanism.

The fact is that the global revision number doesn't really tell you
anything much about changes made to a particular file. It's really just
a substitute for a tag.

-- Brane
Received on 2009-12-27 18:11:45 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.