RE: 'Nested' working copies

> Well, in this area, Subversion is some unknown number of years
> *ahead* of ClearCase, since CC does not offer transactions at all,
> nor have I heard any promises to do so.

Exactly! Ok, it transactions (internally) the individual checkins etc, but there is no notion of transactioning a 'set' of changes. My tool has a 'deliver' comand (terminology borrowed from their UCM model and is kinda analogous to a 'commit') which does the grunt work of making sure the workview is up to date ('rebased', kinda analogous to 'update') and then locking the stream we branched from, merging back, putting down a label, sending mail, etc etc (tons of stuff is happening). By carefully handling the sequence of things I can achieve close to simulated atomicity, but if I get unanticipated errors I just bail out, for manual cleanup - too hard to write code for all possible issues. Still, it works 99.9% of the time so...but it'd be nicer and easier to do things if it was helped by CC...

> Likewise, CC does not allow
> anything like svn:externals (nested repositories/workspaces), unless
> you're willing to count "versioned symlinks."
>

Ugh. As noted, using hard/symlinks in CC are more trouble than it's worth usually. Nesting, as such, does not concern me personally that much since my tool handles the creation of a CC view nicely. And, my build system connects the components wherever and hwever they may be located.

Ok, so maybe svn won't replace CC anytime soon, certainly not for inhouse use, but Svn is (to me) a no-nonsense solution that gives the minimum I crave for keeping source etc organized and allow me to go the route of open source (both to use and to provide). CC won't touch that segment much unless they start giving it away...

Thanks for your response,

ken1

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 23 21:17:17 2003