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

Exporting/Importing to Multiple Repositories

From: Woodward, Gordon (RBC Dexia IS) <gordon.woodward_at_rbcdexia-is.com>
Date: Tue, 20 May 2008 11:08:03 +1000

My company is in the process of moving all our source code to Subversion
and what we are planning on doing is having separate repositories. One
repository will be used by all our developers to manage their code with,
the other repository is what will be used for storing all the source
code that gets released to UAT/Production. In essence the second
repository will be used as an external tagging system.

Is anyone using Subversion is a similar scenario? What process would
people recommend in moving the code between repositories? I've been
investigating using a Nant script to do this process but have a couple
of problems I'm trying to find solutions for. The dev repository makes
heavy use of a common library with each project stored in Subversion
using multiple svn:externals references to this library. When exporting
the Dev code that is ready for UAT/Production release, I need to update
these svn:externals to point to the common library held in the second
repository. I've been looking at the svn commands and can save the
svn:externals definitions to a text file but the sticking point is the
actual updating of the svn:externals references back to Subversion. Any
advice on the best way to do this?

Regards,
Gordon

____________________________________
This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient(s) is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately and delete this e-mail.

        The contents of any attachment to this e-mail may contain software viruses or other defect which might affect your own computer system once received or opened. While companies under RBC Dexia Investor Services Trust and its affiliates take reasonable precautions to minimize that risk, we cannot accept liability or responsibility for any damage or loss which may occur or be sustained as a result of a software virus or other defect. You are responsible for virus checks before opening any attachment.
Received on 2008-05-20 06:44:25 CEST

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.