On 17 June 2012 02:39, Joseph Moackler <jmoackler_at_gmail.com> wrote:
> I use TortoiseSVN to keep up-to-date on an addon for a game. The authors of the addon use subversion on their working copy. They have two separate trunks, one for their main addon install and one for the libs required for the addon to run. Both of these are required to be in the same folder in order to run in the game.
> Is there anyway to setup TortoiseSVN to do a fully recursive update in one folder with both the main addon and lib trunks without having to delete the .svn folder and going through the checkout process twice? Both "projects" do not have similar named folders and are made so they don't.
You cannot have checkouts from two separate repositories in the same
folder, so you'll have to use another workaround. My suggestion is
Create your own local repository with one game folder in and check that out.
Add svn:externals properties to that folder to pull in the folders
from two separate repositories.
Add a post-update hook for your local repo which copies the relevant
files into a common folder.
Updating this working copy should then update the two separate
components and copy them to a common folder in a single action.
An alternative would be to write a script to run the svn command line
tool and make it svn export the files directly from the remote repo
into a non-versioned common folder. This obviously uses more bandwidth
because it unconditionally pulls down the whole file every time.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-06-18 10:24:46 CEST