Re: CVS and Jar files: Should you import Jar into the Repository? Why or why not

[Greg A. Woods]

[ On Tuesday, March 5, 2002 at 20:22:01 (GMT), Richard Caley wrote: ]
> Subject: Re: CVS and Jar files: Should you import Jar into the Repository? 
> Why or why not
>
> Bollocks. The core task of CVS is version control.

You're so wrong I don't even know where to start.

> The abiliy 
> to get a diff is nice but way, way down the list. 

Until/unless you understand the fundamental nature of RCS files and the
fact that CVS is merely an RCS front-end, you won't even have a clue why
you are so wrong.

> I want to be able to build the system as it was last week.

Very good -- that's one of the reasons for using version control in a
software configuration management process.

> That means
> version control on all files used in the build where that is at all
> possible.

Yes, that's a pre-requisite to being ablt to reproduce your builds.

> I'd shove system libraries and the kernel in there if I
> could. Certainly I want third party libraries if I can and test data
> always.

Uh huh.

Clearly you don't seem to understand that CVS is just one of the many
tools you will need if you wish to accomplish all you desire.

CVS does not, and never ever will (unless it becomes something different
than it is today), be suitable for use in tracking changes to
non-diff-able and non-patch-able files.  (among the many other things
it's also not ever going to be good at and wasn't designed to do)

-- 
                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>