Problems And Solving

It is ok to version control symlink files as long as only "ci -l" is used, not "co".

You can also "rcs -l" symlink files too — links are still there.

Actually, both "ci -l" and "ci -u" are ok. But the problem with "ci -u" is that you have to refer to "co" for help when you need to change. But when you check out, whether locked or unlocked, the link will be gone.

documented on: 2006.12.28

It is ok to version control symlink files as long as only "ci -l" is issued, and no vcs tag update occurs within the file, just as what I've been doing for /export/sysback/files.

After co (even if -u), the symlink file will be overwritten as a real file, thus the link is lost.

$ dir p5903/p-ml-apics.tex p-ml-apics.tex
lrwxrwxrwx    1 tong     tong           20 Oct  5 16:43 p-ml-apics.tex -> p5903/p-ml-apics.tex
-rw-r-----    1 tong     tong        36619 Oct  5 16:44 p5903/p-ml-apics.tex

$ co -f -u p-ml-apics.tex
RCS/p-ml-apics.tex,v  -->  p-ml-apics.tex
revision 1.6 (unlocked)

$ dir p5903/p-ml-apics.tex p-ml-apics.tex
-r--r-----    1 tong     tong        36619 Oct  5 16:46 p-ml-apics.tex
-rw-r-----    1 tong     tong        36619 Oct  5 16:44 p5903/p-ml-apics.tex

documented on: 2001.06.09 Sat 17:47:10