At 9:50 PM -0700 10/25/01, Martin McClure wrote:
>At 7:28 PM -0700 10/25/01, Martin McClure wrote:
>>
>>Don't have a CVS system handy to test this assertion, so I'm going 
>>only on memory here, but changing permissions in your working 
>>directory and then committing should work OK. You might have to use 
>>the -f option on your commit to force the change to actually take 
>>place if CVS isn't smart enough to notice that the files had 
>>changed (you normally can't commit a new version unless you've 
>>changed the file. The -f option says 'make a new version anyway.')
>
>Hang on... experimentation indicates that won't work. The easiest 
>way to do it is to chmod the repository files directly, but I'm 
>assuming you don't have permission to do that. I'll continue to look 
>for a way to get those files marked executable.

Okay, it looks like removing the file and then re-adding it with the 
execute permission set does the right thing. I used these commands to 
make a script executable in a small test repository:

mv script foo
cvs rm script
cvs commit -m "Temporarily removed script while making it executable."
mv foo script
chmod +x script
cvs add script
cvs commit -m "Re-added the newly-executable script."



I also noticed that there is a binary file (and there may be others) 
that CVS doesn't know is binary, platforms/Mac OS/vm/resources.sit

You can mark it binary in CVS by doing:

cd platforms/Mac\ OS/vm
cvs admin -kb resources.sit

This should be all you need to do if you originally imported from a 
Unix client. If you imported from a client platform with different 
line end conventions the file in the repository may be mangled and 
should be updated.

-Martin