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

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.
Some of our projects are structured like this (MS Windows):

D:\Source\Project1
D:\Source\Project2
D:\Source\CommomLibraries

Where Project1 and Project2 are individual projects but both rely on files
which reside in D:\Source\CommomLibraries and should reside there.

One could try to use svn:externals not to set this up properly so that a
Checkout of Project1 also checks out CommonLibraries and a update on Project1
also takes into account the changes you've made to CommonLibraries.

For me it seems that SVN 1.7.x currently cannot do this. What it could do is to
place the structure described above on the repository in the same way, but in
the working copy the COmmonLibraries folder would have to reside below each
Project folder:

D:\Source\Project1\CommonLibraries
D:\Source\Project2\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
svn:externals like I assumed would work. It even commited the structure
properly to the repository. But when I tried to checkout this project on
another computer I get a assertion from svn itsself.

In File
 »D:\Development\SVN\Releases\TortoiseSVN-1.7.5\ext\subversion\subversion\libsvn_wc\wc_db.c«,
 Zeile 2890: Assert-Anweisung schlug fehl
 (svn_dirent_is_ancestor(wcroot->abspath, local_abspath))

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,
Or would such a feature be a candidate for a feature request so we can get this in the future? If it get's a feature request, what actions can I do to speed up ist implementation? (programming it/submitting patches is unfortunatelly out of the question)

I really would not need absolute paths, relative paths would be sufficient, even if these
only supported a single level (../ is sufficient for me).

Best regards

Markus Humm

EB-EV
Entwicklung Elektronik

ebm-papst Mulfingen GmbH & Co. KG
Bachmühle 2
74673 Mulfingen

Phone.: +49 (7938) 81 531
Fax: +49 (7938) 81 9531
mailto: Markus.Humm_at_de.ebmpapst.com
http://www.ebmpapst.com

GreenTech - Ein Zeichen, mit dem wir Zeichen setzen. A symbol that defines standards.

ebm-papst Mulfingen GmbH & Co. KG
Sitz der Gesellschaft: Bachmuehle 2, D-74673 Mulfingen
Kommanditgesellschaft Sitz Mulfingen: Amtsgericht Stuttgart HRA 590344
Komplementaer: Elektrobau Mulfingen GmbH, Sitz Mulfingen, Amtsgericht Stuttgart HRB 590142
Geschaeftsfuehrung: Hans-Jochen Beilke (Vorsitzender), Thomas Borst, Hans Peter Fuchs, Dr. Bruno Lindl, Thomas Wagner
Received on 2012-03-01 16:54:09 CET

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.