I pretty much agree with your views on RCS.  I don't think I've ever run
into a group who uses RCS on its own for a large project.  I use
Rational's ClearCase at work which is wonderful.  I thought RCS might be
a good choice in this instance based on how Steve described what he
wanted to do.  If you're just working on a project on your own and are
just maintaining revisions of files, it might not be worth the trouble
of learning and setting up a full-blown cvs repository or something
similar.  But lots of options are always good.

Incidentally, what's PRCS?  I've only used ClearCase and CVS (RCS).  Is
it commercial?  CVS seems to be the system of choice at the moment for
opensource development, but there's a lot of functionality it's missing
that ClearCase has which makes life a lot easier.

Ken

Warp wrote:
> 
>   Don't want to start a version control system war here, but I would like
> to mention my experience about the subject.
>   In the project we are working we used RCS at the very beginning and it
> was a real pain in the a** to use it. Every directory have to have its own
> RCS directory and trying to share the files with all the other members of
> the project was really tedious and difficult. RCS also doesn't allow for more
> than one person to modify the files at the same time. You can't have a
> local copy of the project, which you can modify and then check in to the
> version controlling system, but you have to edit them in a shared file system
> (of course you can copy the files to yourself, but since RCS doesn't support
> this, it's a pain). The locking of files is tedious because you have to
> always remember to unlock the files that others may want to change.
>   Then we changed to PRCS. What a heaven! All the directory structure could
> be checked in to one single project file. You can have many sub-projects so
> that you can work with intermediate versions that do not interfere with the
> main version. More than one person can edit the same files at the same time
> and PRCS can merge the files afterwards without problems (the problems only
> arise if the persons edited the same lines of the files, which should be
> avoided, but if they edit different lines, there's no problem at all).
> Sharing the files with all the other members is very easy (every member
> can have the latest version of all the subprojects with one single checkout).
> Every member can have a local copy of the project (or any number of copies
> if wished), only the main project file has to be shared. You don't have to
> worry about locking and unlocking files; you just edit them and check them
> in, that's it.
> 
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message