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

Feature request

From: Humm, Markus <Markus.Humm_at_de.ebmpapst.com>
Date: Fri, 2 Mar 2012 14:18:21 +0100

Hello,

we are currently in the process of implementing subversion on our site and I have found out
it lacks one feature I'd really love to use: relative local paths for svn:externals.

I already started a discussion about such a feature over in the user@ mailing list, and
after a little discussion I got the suggestion to write about my wish here and start a
discussion here.

I know that there are other possible solutions for my problem, but none of those seems to
have the elegancy and simplicity a svn:externals based solution would have! They're either
failure prone (user errors) or would require to use OS level commands/techniques which are
Unfamiliar/strange to normal users here which wouldn't increase trust in a SCM solution at
all!

Here's what I'd like to do:

Given the following directory structure (on Windows):

D:\Source\Project1
D:\Source\Project2
D:\Source\Project3
D:\Source\CommonFiles

where each Project directory contains one working copy and relies also on files from CommonFiles
and all of those projects and CommonFiles are from the same repository.

I'd like to be able to specify on Project1 ../CommonFiles as local path of the svn:externals
property. I can understand the security concerns raised over in user@, but for this the feature
should either

a) have a global switch in the client to disallow usage of ../ completely
b) have the possibility to specify a list of "trusted" domains/URL which may contain ../ paths
   and for all other repositories ../ as local path for svn:externals would be illigal
c) A combination of a) and b) so you can switch it off even if a "trusted" list exists

I don't mind a) or b) either would be fine with me.

Another security meassure could be built in I'd be ok with as well: limit relative local
svn:external paths to one single hierarchy level: ../CommonFiles would be allowed but
../../ would be illegal. So for my example nothing could leave d:\Source with that limit.

I hope my wish has been well enough written to be understandable. If not feel free to
contact me for further clarifications.

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-02 14:22:50 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.