We've have had a similar issue as the code base became large. We have
created a lightweight tool using Perl scripts, called YaM
(http://dartslab.jpl.nasa.gov/yam), that is built on top of a SVN/CVS
version control layer to solve this problem. YaM supports the concept of
"link modules". With YaM, a user's sandbox typically consists of a small
number of "work modules" - ones checked out from SVN repository, with
the rest being link modules derived from previous releases of the
modules. As the name suggests, link modules show up as links to external
files in your sandbox and are fast to create.
The link modules do not update automagically in the user sandbox. The
user can however update to newer versions when he/she chooses to. The
idea is to isolate the user's development from changes in the
surrounding code until the user is ready to absorb them. YaM allows
users to bump up the link module versions at any time in their
sandboxes. This overall approach works quite well for us and some other
software teams that have gone this way.
Abhi
On Sat, Apr 14, 2007 at 10:38:22PM +0800, lawrence yang wrote:
> Hello,
>
> I am a SCM admin of clearcase and begin to learn svn now. subversion is
> perfect except one point below.
>
> 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.
>
> Without above concern resolved, subversion will never take the place of
> clearcase in the development of large project.
>
> 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. There are millions of
> such compile interim file after a full build, how subversion can prevent
> these file from being submit?
>
> Cheers,
> Larry
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
--
Abhinandan Jain, Ph.D.
Dynamics and Real-Time Simulation (DARTS) Lab
Mobilty and Robotic Systems Section
Jet Propulsion Laboratory
4800 Oak Grove Drive, Pasadena, CA 91109
(818)-354-3412 (818)-393-5007 (fax)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 20 15:07:16 2007