Question about RCS files
Hi. I am a CVS newbie and I would like to do/have the following: There is a Server with an CVS Repository sv in the path /var/lib/cvs/sv. On the clients I work with: CVSROOT=:ext:[EMAIL PROTECTED]:/var/lib/cvs; LOCAL=/SOMEWHERE/sv; CVS checkout is done by: cd /SOMEWHERE; cvs -d $CVSROOT checkout 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; 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?). 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? Thanks a lot for any help in advance! Greetings, K. Posern. ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Question about RCS files
K. Posern [EMAIL PROTECTED] writes: 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? CVS doesn't have support for that. You'd have arrange to update any separate checked-out versions on the server yourself using a script. Take a look at the hooks like 'commitinfo' and loginfo' for ways to do that. -- Brian Gough Network Theory Ltd, Publishing the CVS Reference Manual --- http://www.network-theory.co.uk/cvs/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Question about RCS files
Hi. I am a CVS newbie and I would like to do/have the following: On the clients I work with: CVSROOT=:ext:[EMAIL PROTECTED]:/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 ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Question about RCS files
Hello, * On Thu, Aug 26, 2004 at 12:20:14PM +0200 K. Posern wrote: 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). Have a look at C.3.5.2 of your manual: https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_18.html#SEC175 HTH, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Question about RCS files
K. Posern wrote: 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? You have to do a cvs-checkout into a separate directory on the server, and then perform a cvs-update every time a client does a commit. In UN*X you can do the checkout on a cron job periodically. In Windows I think you can use cygwin to set up a cron job as well. You could also abuse the loginfo script so that after every commit the server runs a cvs update in you checked-out directory. See https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_18.html#SEC167 Cheers, Andrew Thomas ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
