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

Re: Good SVN practices with multiples submodules

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-05-28 14:35:09 CEST

On 5/28/07, Mathieu Malaterre <mathieu.malaterre@gmail.com> wrote:
> Hello there,
> I have the following issue. We currently have the following layout
> for our CVS server:
> cvsroot/
> app1/
> app2/
> ...
> modules/
> module1
> module2
> module3
> ...
> Where appX can use moduleY and/or moduleZ. Every time an appX is
> validated: it is branched. But one has to *manually* make sure that
> all modules used is also branched using the very same tag.
> I would like to know if there would be any easier (transparent) way
> of doing that in subversion ? (there is not symlink on a subversion
> server, right ?).

In Subversion with nothing extra? No. But if you use svncopy.pl to
make the branch, it'll update the externals to point at your "modules"
at the current revision (based on how I read the README file anyway).
See http://svn.collab.net/repos/svn/trunk/contrib/client-side/svncopy/svncopy.README

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 28 14:36:00 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.