[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS corrupts binary files ...

From: Tom Copeland
Subject: Re: CVS corrupts binary files ...
Date: Thu, 17 Jun 2004 16:25:02 -0400

On Thu, 2004-06-17 at 16:12, Greg A. Woods wrote:
> >  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.

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?

> Then you need only program your build system to refer to the appropriate
> directory for the appropriate components 

Why bother with that?  Just put the jar files in myproject/lib and point
the Ant script to them.  And if we've got a FAR_OUT branch that uses
foolib-0.3.jar, that jar file is in that branch and the Ant build.xml
there points to it.

> and if your build system is
> anywhere half decent you'll simply check in the build system
> configuration source file(s) and tag them.  

Yup, makes sense.

> 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.

Yup, that's what's happening now.  Maybe we're converging...



reply via email to

[Prev in Thread] Current Thread [Next in Thread]