[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Subversion vs. Clear Case

From: Janulewicz, Matthew <MJanulewicz_at_westernasset.com>
Date: 2005-07-05 19:20:53 CEST

At the same time, though (was a CC admin for three years) the dynamic
views can help greatly in an XP environment (and by that I mean eXtreme
Programming, or whatever the kids are calling it these days.) Many quick
changes, you want them all, now now now, without having to sync all the

From a CM standpoint, especially nightly builds, it's nice because you
always have the latest code. There is no notion of a sync or a get.
Label and go. (but let's not talk about how long labelling takes ;) )

Lastly, as mentioned below, if you have a very, very, very huge build,
say one that has to be built across different platforms (multiple Unix),
the ClearMake utility is a godsend. Saves mucho time. Relatively useless
on smaller PC type builds, but on large enterprise sized web deployment
java etc. system builds, it pulls its weight.

It may also be worth it to note that you can arrange your dynamic view
to 'pull' (view) any code you want, not just the latest. And the
resolution is down to single files. In other words, you can say 'I want
all the code from label XX, except this one file which I want to be the
latest at all times.'

Again, not for everybody and overkill for most folks, but in some cases
the huge price tag is worth it. Dynamic views aren't as nutty of an idea
as it may seem on the surface. The idea of a source control tool that
runs as a mountable, dynamic filesystem just had a sort of 'neato'
factor with me.


-----Original Message-----
From: bob@proulx.com [mailto:bob@proulx.com]
Sent: Tuesday, July 05, 2005 9:33 AM
To: users@subversion.tigris.org
Subject: Re: Subversion vs. Clear Case

Didier Trosset wrote:
> Dynamic Views ...
> From my point of view, I guess things happened this way: One day, a
[...very interesting discussion...]

> halted by a 15 minutes compilation.

I also think that much slower compilation machines than we have today
played a roll in the design. And flavored by also having a bunch of
identically configured machines. If someone else on the network has
already compiled that file, usually the one committing, then "why
compile it again" and so the dynamic view with the version filesystem
caused it to appear immediately already compiled. If your project
takes hours to compile then this has the potential to save a huge
amount of time.

But today's computers are much faster. One of the large projects I
work on used to take several hours to compile but is now down to ten
minutes for a complete project rebuild. Saving the compilation time
of a single object is not as critical today as it was then. This
causes a different optimization in build system design today. And
sharing compiled objects means that you must ensure identical systems
which is another problem.

> Don't know if my story hit the point. But what I guess is that
> has been started from the idea of having dynamic views. Then
> else in ClearCase has been developped to circumvent this weird idea of
> dynamic views.

Very plausible.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

E-mail sent through the Internet is not secure. Western Asset therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Western Asset therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 5 19:43:45 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.