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

Re: Multi-module repositories

From: Martin Eisenhardt <martin.eisenhardt_at_wiai.uni-bamberg.de>
Date: 2005-11-18 17:02:27 CET

Hi Peter,

I think what you are looking for are svn:externals. Take a look at the SVNBook


In your case, it might be appropriate to define a new project module-BC with
the following svn:externals properties on its trunk-directory:

        module-B file:///repository/module-B/trunk
        module-C file:///repository/module-C/trunk

This way, both projects are checked out into one common working directory

        svn checkout file:///repository/module-BC/trunk modules-BC

and you can happily work with both of these.

Kind regards
Martin Eisenhardt

On Friday November 18 2005 16:50, Peter Herth wrote:
> Hi,
> I have the following situation working with svn and wondered, whether
> there is an easy way to do the following that I am overlooking.
> I want to put a large software project into one subversion
> repository. This project consists of modules - so far these
> modules were independant CVS modules. So my svn repository
> might look like:
> repository/
> module-A/
> trunk/
> files-of-A
> module-B/
> trunk/
> files-of-B
> module-C/
> trunk/
> files-of-C
> In reality, there would be many more modules, but I usually want
> to only check out a few selected ones from the repository into a
> directory called "work", eg:
> svn checkout file:///repository/module-B/trunk module-B
> and perhaps
> svn checkout file:///repository/module-C/trunk module-C
> so that my work directory looks like:
> work/
> module-B/
> files-of-B
> module-C/
> files-of-C
> now that works, but to do an update/commit on any change of B and
> C, I do have to go into the corresponding subdirectories and do an
> update or commit there. In the case of update, this is merely
> inconvenient, but imagine, a change of a file of B and one of
> another file in C are actually one operation. So being able
> to perform a single atomic commit on the change would be great.
> (If it would not be possible to perform an atomic commit, then
> there would be no real reason to keep the two modules in the
> same repository in the first place).
> Peter
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

Dipl. Wirtsch.Inf.(Univ.) Martin Eisenhardt
Otto-Friedrich-Universität Bamberg
Fakultät Wirtschaftinformatik und Angewandte Informatik
Lehrstuhl für Medieninformatik
D-96045 Bamberg
fon: +49 (951) 863-2856
fax: +49 (951) 863-2852
www: http://www.mneisen.org
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 18 17:05:38 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.