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

Re: subversion demerits in comparison with clearcase, can any expert advise on this?

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2007-04-16 12:01:28 CEST

On Saturday 14 April 2007 16:38, lawrence yang wrote:
> The project of our company is huge and there are too much source files to
> be compiled/linked, we currently use clearcase dynamic view to build the
> whole project. But if subversion, the only way to build whole system is to
> check out all source files to an local directory and build. It will take
> too much extra time to check out all the source files to local computer. Is
> subversion have some feature like clearcase dynamic view? Can I just check
> out one or two file, modify the file and then compile/build the whole
> system?
>
> This is also important to all developers. Individual developer sometimes
> just modify one or two file to fix bug, but they must checkout millions of
> files into local directory if use subversion.

If your application requires millions of files to build and you can't compile
different modules/libraries separately, then you somehow need to provide
those files to the compiler. In that aspect CC is the same as SVN, just that
maybe CC hooks the filesystem and only fetches the actual data on demand -
it's not entirely clear to me what those dynamic views are.

However, you typically only checkout once and then simply update your working
copy, i.e. you keep the workingcopy itself across different changes and
builds.

Now, if you want to checkout fresh in order to make sure that no remains from
former builds have any influence, you might be able to use 'export' rather,
although that doesn't create a workingcopy but just a simple filetree.

> BTW, quite some compile interim file (such as .o file) generated if
> developer build/compile in subversion local copy. When they submit, It
> seems all this compile interim file also submited.

When you commit a working copy, only those files that you previously
explicitly(!) added are included. Using 'ignores' could help with maintaining
that, as using a graphical client could. Subversion itself does not version a
file just because it is in a working copy though.

> There are millions of such compile interim file after a full build, how
> subversion can prevent these file from being submit?

No need, it already doesn't include files not explicitly added! If those
really are part of your repositories, you possibly imported a sourctree
already containing them or something like that, but it doesn't "just happen"
automatically.

Uli

-- 
Sator Laser GmbH
Geschäftsführer: Ronald Boers, Amtsgericht Hamburg HR B62 932
**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 16 12:00:38 2007

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