[Top][All Lists]

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

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

From: Chris Cameron
Subject: RE: How well does CVS handle other types of data?
Date: Fri, 13 Jul 2001 10:01:19 +1200

But Greg, you say CVS is a source code management tool (really an ASCII text
file management tool, given all the caveats you add) and the manual excerpt
you quote says CVS is 'a version control system'.  A version control system
DOES NOT IMPLY source code management.  A version control tool allows you to
control and recreate versions.  Merging is an added feature.  For us, the
biggest plus for CVS is that it will manage multiple files and directories
(even if it doesn't version directories, we can manage that).  We started
using CVS after investing a lot of effort to reinvent it in a minimal form
on top of RCS!

You've already told people to use CVS (a version control system) for
managing their source and then find ANOTHER version control system (or make
their own) for managing binary (or non ASCII text) files.  THey are saying
that they already have a version control system in CVS and why should they
need to operate two version control systems.

You keep saying to find the screwdriver instead of using the hammer, but
a. is it really a hammer for a screw?  It is still being used for version
control.  The users have decided the 'merge' features are not important, it
is the version control they want.
b. where do they find out about screwdrivers?  Are there any screwdrivers or
only your hammer plus string and glue solution?

Now you'll probably tell me to go and find a screwdriver as well!  I
generally find your posts interesting and informative, but on occasions you
seem to be opposed to what everyone else on the list wants and your opinion
is inviolate.

Chris Cameron                       Open Telecommunications Ltd
Product Manager                           IN Product Management
address@hidden                           P.O.Box 10-388
      +64 4 495 8403 (DDI)                          The Terrace
fax:  +64 4 495 8419                                 Wellington
cell: +64 21 650 680                                New Zealand
Life, don't talk to me about life ....(Marvin - HHGTTG)

> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> Greg A. Woods
> Sent: Friday, 13 July 2001 8:38 a.m.
> To: Peter Fox
> Cc: CVS-II Discussion Mailing List
> Subject: RE: How well does CVS handle other types of data?
> [ On Thursday, July 12, 2001 at 11:38:21 (-0400), Peter Fox wrote: ]
> > Subject: RE: How well does CVS handle other types of data?
> >
> > Sorry my "graphic people" are the same people who are writing
> Delphi code.
> So, have someone put on a virtual "graphics people" hat!  What's the
> problem here?  That should make things easier, not harder!!!!!
> > IMHO the people who say "get your binaries out of my merging system" are
> > looking very much as CVS as a tool to control parallel
> development of source
> > code. CVS becomes a technique for applying patches to a
> development thread.
> Yes, that's exactly what a source code management tool is.  CVS is a
> source code management tool that assists users in merging concurrent
> changes to files, be they concurrent edits on the same branch, or
> not-necessarily-temporally-related changes on separate branches.
> A "commit" is literally the addition of a "delta" to a branch!  All CVS
> does is keep track of branches and revision relationships in groups of
> source files.  That's it.  That's all.  That's enough.
> > IMHO the people who are saying "I need to put binaries in CVS"
> are looking
> > at using CVS for managing a project. i.e. they want to be able to have a
> > single repository that they have confidence stores all the
> items needed to
> > produce a release.
> I hate to say this again, but RTFM:
>     What is CVS?
>     ============
>        CVS is a version control system.  Using it, you can record the
>     history of your source files. [[....]]
>     What is CVS not?
>     ================
>        CVS can do a lot of things for you, but it does not try to be
>     everything for everyone.
>     CVS is not a build system.
>     CVS is not a substitute for management.
>     CVS is not a substitute for developer communication.
>     CVS does not have change control
>     CVS is not an automated testing program
>     CVS does not have a builtin process model
> > CVS becomes not just a developers tool but also an
> > essential part of the release mechanism. It allows the developers, build
> > people, system testers and customers to agree what they are looking at.
> Yes of course.  CVS keeps track of branches and revision relationships
> in groups of source files.
> A "project" which produces products has many things more than just
> source files, and many more tools than just a source code control tool.
> It is the build system and the configuration management tools which give
> project managers the ability to reliably reproduce products from known
> sources.  All CVS does is keep track of the related source code
> revisions necessary to produce such a reliable repeatable build.
> > It is also a tool to enable developers to retrieve all the
> components that
> > they need to be able to develop. Writing the development
> procedures and the
> > like is just so much easier with a single repository.
> Yes, CVS is that.  It is just _ONE_ tool though, of all those neccessary
> to have in a project management toolbox.
> --
>                                                       Greg A. Woods
> +1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
> Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

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