[ On Thursday, June 17, 2004 at 15:49:39 (-0700), Paul Sander wrote: ] > Subject: RE: CVS corrupts binary files ... > > Nope, I got it. The thing is, you can control pointers (e.g. makefiles > containing references to files stored in a library somewhere) all you > want, but that buys you nothing unless the targets of the pointers are > also tightly controlled.
No, you didn't "get it". You seem to be among the many people who always forget to keep in mind what CVS is _not_. For example: CVS is not a complete software configuration management system. Most folks don't expect their C compiler to track changes to files any more than they expect their Make program to compile C code or interpret Python code. Anyone using CVS as a change tracking tool _must_ have some encompassing software configuration management system as well. If that encompassing SCM system does not have "tight control" over _all_ of the components and procedures and processes used in the production of the software products then it is certainly not the fault of CVS. Also what you and many other folks seem to forget as well is that manual procedures and processes can be far easier and more effective than canned software tools for implementing some parts of a complete SCM system. Furthermore those who expect one tool to do everything for them are living in a world of pure fantasy. Software development is first and foremost a process driven by people, not just other software. -- Greg A. Woods +1 416 218-0098 VE3TCP RoboHack <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]> Secrets of the Weird <[EMAIL PROTECTED]> _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs