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

external in reverse

From: Ignacio G. T. <igtorque_at_nucleocc.com>
Date: Mon, 8 Jun 2009 07:13:45 -0700 (PDT)

[I'm re-posting this via web, as I posted it via e-mail on Friday and apparently fell into a black hole...]

I have the following interesting situation:

I work on some projects whose versioned files must be, as workcopies, in completely different paths inside our Windows boxes. Something like this:

C:\Projects\My\Gizmo and subdirectories -> many versioned files
C:\Tornado\target and subdirectories -> a few versioned files

Conceptually, the second tree should be a sub-tree of the first one: when I tag a version, it should refer to a precise photograph of both trees, when I branch, it should branch both trees, etc. But Windows does not have real links, and I haven't
found a satisfactory solution yet (well, actually I'm playing with something called linkd.exe, but there are some quirks.)

I would be happy with a kind of "external in reverse": when I pull C:\Projects\My\Gizmo from a repo, it should also pull C:\Tornado\target from the same repo. And an "amplified external in reverse" would be perfect: pushing C:\Projects\My\Gizmo should also push C:\Tornado\target.

How would you work around this situation?
Would you migrate to Linux :-)?
Would you use some new reincarnation of olde MS-DOS join / subst?
Would you implement some kind of clever hooks and/or local batch files?
Would you modify the svn files to implement the external in reverse?
Would you maintain two separate repositories and perform some clever tricks to "sync" them?

--
Saludos
Ignacio G.T.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2360296
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-08 16:28:58 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.