Re: CVS vs ClearCase, was RE: cvs -n update vs cvs diff

[Noel Yap]

--- "Johnson, Susan" <address@hidden> wrote:
> I'm used to ClearCase, where a person worked within
> a
> dynamic view and you could build, label (tag),
> branch,
> merge and do everything within the same workspace.
> 
> How does CVS differ from that model?

This is pretty much how I use CVS.

One big difference between ClearCase's dynamic views
and CVS is that, for files that are not checked out
(ClearCase meaning), when someone checks it in, you'll
see the changes automatically by default.  CVS's
working directories work more like ClearCase's
sandboxes (I think this is the right term).

Personally, I never liked the default dynamic view
behaviour since it meant less control over what I'm
working with (eg someone can break my build at an
inconvenient time).  At one point, I toyed around with
the idea of changing the config spec so that LATEST
meant 'now' (ClearCase meaning).  Doing so would've
given me the benefits of dynamic views (eg file system
access to the repo) with the benefits of static (I
like this terminology better) views (eg control over
what's in my working directory).

HTH,
Noel

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/