Re: RCS vs SCCS?

Scott Miller wrote: > The O'Reily book _Applying_RCS_and_SCCS_ is a good source of information. > I agree with this choice for a book. Until it came out I only messed with RCS a little, and groaned over SCCS. The book really shows you how to set up either. The only bad part about them is that you'll end up getting or writing wrappers, as another post has indicated. I wrote all my own wrappers, which are nothing more than a bunch of shell-scripts with a lot of the pathing set up in advance, otherwise you have to spend a lot of time explicitly pathing files, unless you want them in an RCS directory beneath the current directory. I am able to survive with the basics of RCS without really having to do anything to the source to make it work. RCS is painless compared to SCCS, and as the book will point out, is supposedly superior. You can get RCS for Windows NT too. And RCS can be used for binaries and other non-ascii files too...I learned that one by accident. But you could store Word documents or others I suppose with it. In the grand scheme of things, if you're going to do serious source code control, you'll soon find RCS and SCCS lacking, unless you do a lot of experimentation. For basics, I recommend RCS--just my opinion. :-) Another good alternative is PVCS, but it's pay ware. RCS seems to behave a lot like PVCS--or is it PVCS behaves a lot like RCS? I've had good experience with PVCS. Anyway, get the book even if you move on to payware, for a really good resource on source code control. just my 2 cents... -- \\\\|// (6 6) ==============================---o00--(_)--00o---============================ Tim Schaefer (800)587-9502 http://www.gate.net/~tschaefe The Computer Business Company, Inc. tschaefe@gate.net =============================================================================