"Les Mikesell" <lesmikesell_at_gmail.com> wrote in message
news:4AA8F483.7070801_at_gmail.com...
>>> You may need to adjust your workflow concepts a bit. In CVS, you would
>>> normally use tags to tie a set of revisions together so you can
>>> reproduce the state of a workspace - and in cvs tags are like labels
>>> that you can float around. In subversion, tags are like snapshot
>>> copies and normally are never revised so if your workflow depends on
>>> floating a tag name so you can embed it in scripts you may have to
>>> change a few things.
>>
>> I'd like to add that this concept of "floating tags" is what Subversion
>> has in
>> mind when you say "revision".
>> Each revision consist of a complete, functional state of the project....
>> ideally.
>
> Yes, except you don't get to apply a well-known name to it. So it is hard
> to
> embed the right revision number into an already written script... With
> CVS you
> are generally forced to use tags because each file will have different
> revision
> numbers and you need the tags as labels to identify the right revisions
> for a
> set of files. With svn you can use tags but it is hard to re-use the same
> name
> to identify a state that is ready for some processing step so you need to
> come
> up with some extra workflow steps to pass a tag name or revision number
> around.
> This may not be difficult but if you floated tags in CVS instead of
> making up
> new ones for every change you may need to change your process with svn.
Hmmm ... not sure I understand this concept entirely. I basically use a CVS
tag every time I do a build or a release to "mark" the version of all files
required for that particular build. 99% of the time, this tag is a one time
thing. However, it does happen every-so-often that a build fails b/c
someone forgot to check in a file. So instead of giving it a new build
number once the file is committed, I just retag with the same tag name and
perform the build. Would that concept/workflow cause problems in SVN?
Secondly, I'm a bit confused with the concept of version numbers in svn
overall. I understand that a version relates to the state of the overall
project - not any individual file as in CVS. So if I am working in a
specific file, and want to see a previous version of that file, does that
require the client to download the entire code repository of a previous
version? In CVS, since files are versioned independently, I can easily see
the state of any one file throughout its history, and retreive a particular
revision for that one file and stick with it (ie: sticky tags). Does that
concept still hold true for svn?
Another problem I had read about a while back was with file renaming; I had
understood it not to be fully functional. Is that the case, or was I
misinterpreting information?
Thanks for the info!
Eric
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2393327
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-10 17:51:10 CEST