[TriLUG] RCS

[Rob West]

I usually use the -l option for ci. It accomplishs the same thing (file 
is writeable and version is locked) but provides a little flexibility in 
case I want to leave it read-only.

Rob

Joel Ebel wrote:

> Normally when a file is checked into RCS with -u it loses it's write 
> permissions.  By turning off file locking, you do change this.  In 
> essence the file will always be locked, and thus always writeable.  If 
> you check them all out again with co * they will be writeable.  Then 
> every time you edit it, just check it in with ci -u filename, and it 
> will stay writeable.  I, however, choose to leave file locking turned 
> on since it helps me remember to check it in when I'm done.  But 
> that's up to you.
>
> Joel
>
> H. Crissman wrote:
>
>> I am relatively new to RCS. Is it supposed to change file permissions 
>> and make them read only? Here is what I have done so far.
>>
>> 1. mkdir RCS in ~/scripts
>> 2. ci -u -t-Baseline * (check in all my scripts)
>> 3. rcs -U * (turn off file locking. I am the only one using this system)
>>
>> Now files that were rwx-rwx-rx are r-xr-xr-x. That seems odd to me?
>>
>> Thanks,
>>
>> H. Crissman
>