Feature request: allow for relative working copy paths in svn:externals definition
From: Humm, Markus <Markus.Humm_at_de.ebmpapst.com>
Date: Thu, 1 Mar 2012 16:35:32 +0100
Hello,
I'm currently learning SVN as we're planning to use it here in the near future.
D:\Source\Project1
Where Project1 and Project2 are individual projects but both rely on files
One could try to use svn:externals not to set this up properly so that a
For me it seems that SVN 1.7.x currently cannot do this. What it could do is to
D:\Source\Project1\CommonLibraries
But that is not what I want. What's even more:
I'm using Tortoise SVN 1.7.5 and this one managed to allow me to set up
In File
The local path of my svn:externals was this: D:/u/svnexternaltest2/gemeinsamme_bibliotheken
If I tried to use ../svnexternaltest2/gemeinsamme_bibliotheken instead Tortoise would detect that it contains a .. Or is a absolute path. Obviously either Tortoises or SVN's absolute path detection loginc is not 100% fool proof as well.
Back to my original issue: is there a way to get the structure I want via svn:externals,
I really would not need absolute paths, relative paths would be sufficient, even if these
Best regards
Markus Humm
EB-EV
ebm-papst Mulfingen GmbH & Co. KG
Phone.: +49 (7938) 81 531
GreenTech - Ein Zeichen, mit dem wir Zeichen setzen. A symbol that defines standards.
ebm-papst Mulfingen GmbH & Co. KG
|
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.