[ On Wednesday, June 9, 2004 at 09:35:37 (-0400), Tom Copeland wrote: ] > Subject: Re: CVS corrupts binary files ... > > On Tue, 2004-06-08 at 17:42, Paul Sander wrote: > > Keep in mind also that there's a difference between "binary files" and > > "mergeable files". > > That's a neat point.
Well, it's kind of a pointless point, neat or not. The only thing that's really important w.r.t. whether CVS can manage the file reliabily and without headache is whether diff & patch can reliably copy changes from one version of the file to another _and_ that any conflicts in those copies can be detected and easily resolved by hand. > Most of my Java projects use 3rd party jar files, > which are compressed tar balls, more or less. And I certainly don't > want to try to merge foolib-0.1.jar with foolib-0.2.jar when a new > version comes out; I just want to put it in CVS so that it gets tagged > and exported and so forth. No, you REALLY DO NOT want (or need) to do that. What a waste. What you should do is treat the foolib product files for what they are and to install them as products on your build machines in directories named after their complete version-specific identifiers. Then you need only program your build system to refer to the appropriate directory for the appropriate components and if your build system is anywhere half decent you'll simply check in the build system configuration source file(s) and tag them. Once you've done that then you can check out any release of your source and type "make" and the right components will be combined with your sources to create your final product. CVS is _not_ a build system. CVS is _not_ a complete configuration management system. Please learn to use the right tool for the job!!!! -- 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