Login | Register
My pages Projects Community openCollabNet

Discussions > users > RE: Re: Dumb newby question: moving from RCS

Project highlights: :. Download .: :. Support .: :. FAQ .: :. Translations .: :. Donate .: :. Report Bug .:

tortoisesvn
Discussion topic

Back to topic list

RE: Re: Dumb newby question: moving from RCS

Author postmaster at tigris dot org
Full name postmaster at tigris dot org
Date 2009-01-19 14:39:59 PST
Message Kevin, thanks very much for the explanation. I think you're right in that this is the crux of my problem:

... You'll probably discover that once you master the SVN workflow, you will no longer like the RCS workflow. They are fundamentally different: RCS works on files, SVN works on directory trees (including files and properties).

I [obviously] don't fully understand the SVN-style workflow and I've been through the TSVN docs and part of my problem is that it is trying to explain how SVN works in a complicated environment (with parallel changes and branching versions, etc) and I'm not seeing the simple-enviroment trees for the fancy-stuff forest.

With Perl apps, there's no "make" and "release" -- the checked-in ["committed"] files *ARE* the app, and so part of the workflow isn't clear to me: I have the hierarchy PROJECT. PROJECT/SVN is my repository and PROJECT/PROJECT is where the actual in-production app lives [together with its various "extra" files: logs, docs, config files, etc]. I can easily right-click on SVN, do "check out a copy" into PROJECT/NEWSTUFF, play around, and then do a "commit" on the whole directory [so everything I changed and tweaked would get "checked in" -- that's the right way to do an SVN-styule workflow, yes?]

BUT: in the normal SVN workflow, how would that cycle propagate to producting a new "operational" version? [I'm guess that it would be in this last step [going from a commit in my NEW directory to "refreshing" the master copies in the PROJECT directory, however that happens] that the $REVISION$ and friends would get expanded, yes?

As a side note, I can get by without locking individual files, but I definitely would like to have the master PROJECT/PROJECT directory be read-only [so I don't forget and start editing *them* by mistake -- old habits die hard.]

Thanks again. /b\

« Previous message in topic | 3 of 8 | Next message in topic »

Messages

Show all messages in topic

Dumb newby question: moving from RCS bernie at fantasyfarm dot com bernie at fantasyfarm dot com 2009-01-19 10:46:37 PST
     Re: Dumb newby question: moving from RCS "Kevin Grover" <kevin at kevingrover dot net> "Kevin Grover" <kevin at kevingrover dot net> 2009-01-19 12:36:28 PST
         RE: Re: Dumb newby question: moving from RCS postmaster at tigris dot org postmaster at tigris dot org 2009-01-19 14:39:59 PST
             Re: Re: Dumb newby question: moving from RCS jeanmarc Jean-Marc van Leerdam 2009-01-20 00:27:01 PST
             Re: Re: Dumb newby question: moving from RCS "Kevin Grover" <kevin at kevingrover dot net> "Kevin Grover" <kevin at kevingrover dot net> 2009-01-20 12:49:53 PST
             Re: Dumb newby question: moving from RCS Michael Dixon <michael dot dixon at denovosoftware dot com> Michael Dixon <michael dot dixon at denovosoftware dot com> 2009-01-20 14:44:50 PST
                 Re: Dumb newby question: moving from RCS "Kevin Grover" <kevin at kevingrover dot net> "Kevin Grover" <kevin at kevingrover dot net> 2009-01-20 16:14:20 PST
                     Re: Dumb newby question: moving from RCS Michael Dixon <michael dot dixon at denovosoftware dot com> Michael Dixon <michael dot dixon at denovosoftware dot com> 2009-01-20 17:04:55 PST
Messages per page: