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

Multi-module repositories

From: Peter Herth <p.herth_at_gmail.com>
Date: 2005-11-18 16:50:23 CET

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
Received on Fri Nov 18 16:52:39 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.