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

RE: Multi-modules / subdirectories

From: Bob Archer <bob.archer_at_amsi.com>
Date: Fri, 13 Mar 2009 11:21:32 -0400

How about something like this:

        /Module1 (external)
        /SharedModule (external)
        /Module2 (external)
        /SharedModule (external)
        /Module1 (external_at_350)
        /SharedModule (external_at_350)

Now, when you tag Project1 you can use svncopy.pl and it will pin the
externals in the tag to the current revision of module1 and shared


> -----Original Message-----
> From: webpost_at_tigris.org [mailto:webpost_at_tigris.org]
> Sent: Friday, March 13, 2009 10:56 AM
> To: users_at_subversion.tigris.org
> Subject: Multi-modules / subdirectories
> Hi,
> I am trying to figure out how to use subversion with multi-module
> projects.
> I will try to explain what problems I am trying to do, and the
> I am having.
> I have read several threads regarding this, but there did not seem to
> a real solution, or any news about future development to resolve the
> issues.
> As an example, let's say I have these modules: Module1, Module2,
> SharedModule.
> In practice the number of modules are high, so keep that in mind.
> There is a Project1, which uses Module1 and SharedModule. And there is
> a Project2, which uses Module2 and SharedModule.
> In case of a release I want to tag Module1 and SharedModule with
> "Project1-1.0"
> or Module2 and SharedModule with "Project2-1.0".
> I would like a layout like this:
> /trunk
> /Module1
> /Module2
> /SharedModule
> /tags
> /Project1-1.0
> /Module1
> /SharedModule
> /Project2-1.0
> /Module2
> /SharedModule
> /branches
> /Project1-1.0-updates
> /Module1
> /SharedModule
> /Project2-1.0-updates
> /Module2
> /SharedModule
> The problem I have is how to tag modules for Project1, without tagging
> those
> of Project2. I would have no problem to checking out the modules for
> Project1
> seperately and thus have a working copy with only the modules for
> as version controlled. However then I cannot find any way to tag
> subdirectories.
> I would have to tag Module1 and SharedModule seperately each time.
> would be fine if there were two modules, but since in my case there
> about
> 50 it would be unworkable.
> If only there was an option to do subversion actions, such as
> and merge on subdirectories in a directory that itself is not version-
> controlled
> I would be very happy.
> Since there are about 50 modules, I do not want each of them to have
> own trunk, tags and branches. This also would result in way too much
> ------------------------------------------------------
> 1317549
> To unsubscribe from this discussion, e-mail: [users-
> unsubscribe_at_subversion.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-13 16:22:46 CET

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.