[ On Thursday, June 17, 2004 at 16:25:02 (-0400), Tom Copeland wrote: ]
> Subject: Re: CVS corrupts binary files ...
>
> Hm. Why not simply check these jar files into the repository where they
> can be tagged/branched/exported and so forth? Why should every
> programmer on my team need to get all the versions of each jar file laid
> out on his machine when he could just do a "cvs up" to get the current
> stuff for his branch?
Don't you have a build system? (apparently you do going by your later
comments)
Can't it do all those things for you?
Let me repeat: CVS is _not_ a build system.
Just because you can use CVS to update version-controlled files from
some central repository doesn't mean you should try to use CVS to copy
all types of files from all kinds of repositories.
If you have many and diverse build machines then put your static
(i.e. non-changing) components on a central machine in a public
directory and have your build system invoke the appropriate tool to copy
them into the build environment as necessary. If you do that, and if
the way you reference those components includes information about their
version numbers (e.g. in the name of the directory they're "installed"
in), and if your build system is configured using normal source files
(e.g. text makefiles) that you commit to your CVS repository, then CVS
will track which version of which component is needed for every release.
--
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
