[EMAIL PROTECTED] writes: > > Ok what's the proper way of putting scripts into this > directory that the cvs files can use.
As usual, the answer begins with "That depends...". If you don't care about revision control on the scripts, then you can just copy them into the directory. If you do want revision control, then you need to follow the basic process you outlined with just a few corrections: > - checkout the $CVSROOT/CVSROOT directory > - cvs add buglog.sh file Set the permissions the way you want them now and CVS will preserve them for you. > - modify loginfo to call the buglog.sh file Also modify the checkoutlist file to include your new file. > - cvs commit OK. > - cp ../CVSROOT/buglog.sh,v ../CVSROOT/buglog.sh (???) > - Remove RCS info from buglog.sh (???) No. If you added your file to checkoutlist, CVS should check it out automatically. (And will do so every time to commit changes to it in the future.) If you neglected to do that, simply do so now and CVS will checkout your file when you checkin the change to checkoutlist. > - Ensure correct rwx permissions for ../CVSROOT/buglog.sh A good idea, but it shouldn't be necessary if you set them correctly before checking it in the first time. If you neglected to do that, you can set the permissions on the RCS file and CVS should copy them to the checkout out file in the future. -Larry Jones If I was being raised in a better environment, I wouldn't do things like that. -- Calvin _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
