info-cvs
[Top][All Lists]
Advanced

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

RE: How well does CVS handle other types of data?


From: Cameron, Steve
Subject: RE: How well does CVS handle other types of data?
Date: Fri, 13 Jul 2001 14:20:07 -0500

> From: address@hidden [mailto:address@hidden
> 
> [ On Friday, July 13, 2001 at 08:39:09 (-0500), Cameron, 
> Steve wrote: ]
> > Subject: RE: How well does CVS handle other types of data? 
> >
> > On the issue of whether storing binary files in CVS is a good
> > idea, vs. trying to use "something else" in conjuction with CVS,
> > my experience has been that putting the binary files in CVS works
> > well enough, (apart from the above problem.)  The advantage,
> > (having one tag that you can do a "cvs checkout" and get 
> _everything_
> > you need.)  outweighs the disadvantage, (that files are not 
> mergeable)
> > for us anyway.
> 
> That's a moot point Steve.  If your build system (makefiles, scripts,
> source to tools, etc.) is also checked in to your CVS tree 
> then it will
> be tagged and you can "cvs checkout; make" and you'll still ``get
> _everything_'' but you won't have *any* problems with binary files in
> CVS!

Re-reading my original message, I see I failed to mention those binary
files were 3rd party object code for which we do not have access to 
the source code, yet which are nevertheless required to build our product.  
(Probably still not a good enough excuse for you, Greg, I know, but that's 
ok. :-) Of course if you can derive a file it shouldn't go into CVS at all, 
I didn't mean to imply otherwise.  My binaries are not derivable by me.

Probably I should have just left out the 2nd paragraph of my original email.

-- steve



reply via email to

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