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

AW: Feature request: allow for relative working copy paths in svn:externals definition

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

Hello,

>>
>>> > While it is nice that you have concerns about my security in case
I
>>> > should have to deal with malicious servers,
>
> Not just malicious servers. With a scheme that lets you splatter
files anywhere, anyone who can commit can accidentally or intentionally
kill everyone else's machines.

While I can see your security concerns my intention is to use this
feature only in conjunction with locally hosted servers
(same company, same site, all users know each others) and only a single
hierarchy level deep. I already suggested to limit
this to a single hierarchy level.

>>> > I would prefer to have a choice. Maybe some setting wich allows
me,
>>> > based on the server URL (or if that's too complicated for a
start),
>>> > to allow ../ in local externals paths or disallow this. With such
a setting, SVN would seamlessly allow us to use our current directory
layout while maintaining the benefits of atimic checkins.
>>
>>> Excuse me, but given the layout requirements you seek, can you get
away with symlinks?
>>
>> I'm not sure symlinks under XP are powerfull enough and the use of
them is not easy enough for my colloeagues.
>> I'd really prefer a externals based solution.
> What is wrong with keeping everything under one tree? If you are too
> lazy to re-arrange the paths for includes and linkage searches in your
compiler project/build files, treat each thing that you want in parallel
directories as a component and make your subversion main project files
have nothing but > the externals that drop the components in the right
place - which incidentally gives you a nice single place to control the
branch/tag versions of each thing that you use.

Because keeping everything under one tree ties things together wich do
not have any relation other than via CommonFiles.
In my eyes nothing beats the simplicity and understandability of
svn:externals with one single level deep relative paths
to a directory above. Software should adopt as good as possible to the
existing workflow/structures. There should be no
need to completely rearrange projects just to get what one wants only
because some fear security issues which can be
turned off with a single global "turn this feature off" switch in the
client. Those who like can use it, the rest can
ignore it as the default would be to have it off.

Best regards

Markus Humm

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:55:18 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.