Larry Jones wrote: > > [EMAIL PROTECTED] writes: > > > > I'm not trying to do anything special. Just for some reason, if I > > co/ci a file in my .../CVSROOT dir, other files perms get reset, > > e.g., logtags and taglogs. > > That's because whenever you check in something in $CVSROOT/CVSROOT, > *all* of the administrative files get re-checked out (that's what the > "Rebuilding administrative file database" message that you get during > check in means). Why are you changing the permissions on your > administrative files? I repeat -- what is it that you're trying to do? >
What it appeared to me he wanted, was that his taglogs script would be executable for use in something like taginfo... but that every time he checked a file into $CVSROOT/CVSROOT the permissions on $CVSROOT/CVSROOT/taglogs went back to -r--r--r--. Christopher, may I suggest that it might be informative for you to do the following on the server machine. after a commit of a file to $CVSROOT/CVSROOT do: ls -l $CVSROOT/CVSROOT/taglogs* I think the output would be something along the lines of: -r--r--r-- 1 chris cg 1234 date /cm/SLQ32/ICAD/Repository/CVSROOT/taglogs -r--r--r-- 1 chris cg 1290 date /cm/SLQ32/ICAD/Repository/CVSROOT/taglogs,v but what you want is: -r-xr-xr-x 1 chris cg 1234 date /cm/SLQ32/ICAD/Repository/CVSROOT/taglogs -r-xr-xr-x 1 chris cg 1290 date /cm/SLQ32/ICAD/Repository/CVSROOT/taglogs,v As I mentioned yesterday, CVS will keep the execute bits set on checkouts IFF they are set on the ,v file. Also IFF the execute bits are set on the file in the sandbox, when the following is done `cvs add executablefile; \ cvs commit -m "add an executable" executablefile` i.e., when the file is first added to the repo, then CVS will set the execute bits on the ,v file. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
