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

[Ralph Mack]

Hi, Greg,

> > Both may be true. Unfortunately, that doesn't get me where
> > I want to go. So once again, I get to the point of "put up or shut
> > up" and, as with merge tracking, this is also too big a task for
> > me to contemplate under present circumstances.
>
> Well, the trick is to use the right tool for the job!  :-)
>
> You see if you take the unix tool-building philosophy as your approach
> to the problem then you can use CVS as one of the tools within your
> entire SCM system.  It actually works very very well in that capacity!

I like the Unix tool building philosophy - it scales without excessive cost.
However, I don't want to have to spend a significant amount of time to write
the glue to hold the whole thing together. I'd like to use something that
has conceptual integrity across tools and a common tool interface where the
seams
don't show. There is a difference between "cobbled together" and
"integrated".
You only turn over an SCM to a software team to depend upon if it more
closely
resembles the latter unless you have no choice (sadly the case at present
for
open source). If I had an integrated source environment, integrated build
environment, and integrated development environment - preferably all of them
cross-vendor - I'd be a pretty happy camper.

> > Despite my limited time, I really would like to be involved
> > in a project like this, though. My plan of action will be
> > first to evaluate TCCS to see if it is closer to what I want.
>
> Though in many respects it's not much more of a total SCM
> solution than CVS is, you might also be interested in
> the abilities of Aegis.....

Thanks for the pointer - I'll look into it.

Ralph