From: Johnny Fulcrum
Is renaming a repository as easy as mv <oldname> <newname> at the UNIX command line and letting anyone who has things checked out know they have to fix up all of the CVS/Root files in their sandboxes as well as their ~/.cvspass files if for pserver?
That's almost true. Since/if you're using :pserver: on the server side then
you need to modify "inetd.conf" option "--allow-root=" value. Read this:
http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_2.html#SEC30
Yes That is true! Forgot to mention I have a inetd.conf hack to run a shell to dynamically grab any directory in a certain location and treat it as a repository:
/usr/bin/cvs -f `ls -d /cvs/* | sed -e '1,$s/.*/--allow-root=&/'` pserver
Then I don't have to have the unix admins edit the inetd.conf file... :)
Also consider cvs will use repositories identified by symbolic links and accepts multiple "--allow-root=" options. Consider doing:
mv <oldname> <newname> # new name is hard linked ln <newname> <oldname> # old name is symbolic link
In "inetd.conf" use "--allow-root=<newname> --allow-root=<oldname>" and then access by old AND new names should work concurrently.
concerned about history - but I see nothing in CVSROOT that is depending on the name of the repository...
Don't know about this one myself.
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
