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

Re: Layout of Matlab Subversion Repository

From: Jeremy Pereira <jeremyp_at_jeremyp.net>
Date: 2007-06-29 13:29:46 CEST

On 29 Jun 2007, at 09:11, bennistetter@gmx.com wrote:

> Hi all,
> I suggested creating an extra subdirectory in trunk, which contains
> all the functions, which are called by other functions. The problem
> that arises is that in Matlab there is no real distinction between
> applications and functions. Each mfile can be a standalone
> application (after compilation with mcc) but can also serve as a
> helper function of another application. Sometimes we start to
> design a function as an application and afterwards someone else
> recognizes that he can use this function as part of his application.

So what's wrong with that solution? Just create a library directory
and link it in to each machine directory with svn:externals. Then
place a ban on applications referencing the code from other machine
directories. When developer of machine_a discovers a useful function
in machine_b directory, they simply copy it to the library and
reference it from the library. There needs to be a process defined
so that developers are aware of the changes e.g. so that the
developer of machine_b can change his code to reference the library
if he thinks it appropriate.

There also needs to be strong control over changes in the library
directory, since changing the semantics of things in there can break
other apps. This is a problem you have right now but with your
current structure it is impossible to control.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 29 13:41:48 2007

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.