On Fri, Mar 2, 2012 at 7:54 AM, Humm, Markus <markus.h...@de.ebmpapst.com> wrote: >> >> 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.
Which would need to permit the external part to do the same to be useful. So you could keep going up. >> 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. Then commit a tree that includes things the way you want. Or if they really have no relationship, check them out separately. > In my eyes nothing beats the simplicity and understandability of > svn:externals with one single level deep relative paths > to a directory above. And in my eyes that is insanely dangerous. > 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. You don't have to re-arrange anything (even if your arrangement doesn't make any sense...). You just need to commit a project at the top level that puts your components at the relative positions below where you want them. -- Les Mikesell lesmikes...@gmail.com,