On 4/11/2006 9:21 PM, Will Parsons wrote:
> I am investigating moving our existing revision control system, which is
> based on RCS, to subversion, but am having trouble seeing how to implement
> assigning our own revision ID's to files as they are revised. Under RCS,
> we do this by assigning a tag, so that when a new version of file foo.c is
> checked in, it receives a tag such as FOO_C-00-03, and this tag is used to
> uniquely refer it. The subversion concept of tags as branches doesn't seem
> to lend itself to this. If I understand correctly, each time a file is
> revised, a copy would have to be made of that file only to a new location in
> the repository. This seems to be very awkward for this purpose.
The subversion idea of a tag is that it is a snapshot of the whole
project at a particular point in time. You want a snapshot of a
particular file.
The revision number of the repository at the time the file is checked in
seems to be what you want. For example, if you make a revision, then
check in foo.c, the repository revision will change to 12345; you can
uniquely refer to that version as "/path/to/foo.c at r12345".
If you want to give a symbolic name to the 12345, you'll need to put
together your own scheme to do so; Subversion doesn't support that.
> I have also looked at using properties for this purpose, but since there
> doesn't seem to be a way of extracting the revision of a file whose
> property x = y, this doesn't look like it will work either.
>
> Can anyone suggest how to go about doing this?
Either change your practice so you refer to paths and revision numbers
of files, or develop a simple scheme to store triplets of (symbolic
name, path, revnumber) and make it available to your developers.
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 12 15:56:54 2006