Re: Question about RCS files

[Arno Schuring]

>
> Hi.
>
> I am a CVS newbie and I would like to do/have the following:
>
> On the clients I work with:
>     CVSROOT=":ext:address@hidden:/var/lib/cvs";
>     LOCAL="/SOMEWHERE/sv";
>
>
> CVS update is done by:
>     cd "/SOMEWHERE/sv";
>     cvs -d "$CVSROOT" update -dP;
>
> CVS commit is done by:
>     cd "/SOMEWHERE/sv";
>     cvs -d "$CVSROOT" commit;

cvs -d "$CVSROOT" makes little sense... cvs uses $CVSROOT by default


> I describe all this because I dunno if you might need this information to
answer me the following question:
>
> I thought that the CVS-Tree LOCAL and on the SERVER are IDENTICAL (after I
did an update).
>
> But on the server the files end with ",v" and have all the comments and
version stuff inside.
>
> I now know that these files are the rcs files (the backbone of the cvs?).
more or less. Never touch the files in $CVSROOT


> But I need an exact copy of the version a CLIENT has in its /SOMEWHERE/sv
dir on the SERVER (so without the rcs stuff).
>
> How can I achieve this? Do I have to to do an cvs-checkout on the server
and cvs-update everytime a client did commit something?
>
> Or can I say to the server somehow to keep automatically the rcs stuff
seperate in one dir and an "client-like-copy" of the cvs-repository in
another dir?

See "keeping a checked-out copy"
https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_18.html#SEC175


Arno