Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!mcsun!hp4nl!phigate!ehviea!sun4dts!derek From: derek@sun4dts.dts.ine.philips.nl (derek) Newsgroups: comp.os.msdos.programmer Subject: Re: has anyone used the rcs system from Simtel? Message-ID: <746@sun4dts.dts.ine.philips.nl> Date: 27 Jun 91 12:33:24 GMT References: <3447@ria.ccs.uwo.ca> Distribution: comp.os.msdos.programmer Lines: 37 creider@csd.uwo.ca (Chet Creider) writes: >Has anyone succeeded in understanding how the DOS rcs is intended to >work? When I try to use it, it puts write protection on a file, then >can't delete this file when checking in. Then when checking out, it >encounters the write-protected file and can't overwrite it. None of >the switches on ci or co seem to help, and rcs.exe doesn't either. >Of course all of this can be gotten around with chmod (or whatever >program one uses to change file attributes), but what a nuisance! >I hope I'm missing something, and would appreciate help. >It would help to have the source code. My executables were obtained >from Simtel, but there isn't even a hint as to who did the port there. >Chet Creider >. Initialize the file with rcs -U -i filespec This creates an unlocked file, i.e. the file in the rcs directory is read-only but that in the parent directory can be worked on. On a single-user system, this seems to be the best way. With co and ci always use the -u parameter. This checks in/out the file without doing any locking, and leaves the file editable in the working directory. Files in the rcs directory are always read-only and should only be manipulated by the rcs system (but you knew that anyway didn't you :-) This in empirical - i.e. this is what I do, and these are the results I get. Most of the information came from the help stuff with mks toolkit. I run under MS-dos though. Best Regards, Derek Carr DEREK@DTS.INE.PHILIPS.NL Philips IE TQV-5 Eindhoven, The Netherlands Standard Disclaimers apply.