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

svn:externals repository referencing question...

From: Jeff Vincent <jvincent_at_novell.com>
Date: 2005-09-02 21:51:46 CEST

I think I know the answer to this (because it isn't working), but I want
to be sure I'm not doing something wrong.

SVN has the concept of Externals and Vendor Branches. I DON'T want
users to edit the 3rd party libraries and these libraries don't have
their own SVN repository (that I can access anyway). So... it seemed
that the svn:externals methods is the easiest and cleanest way to
consume these libraries. So we imported the 3rd party libraries into
our own SVN repository and used the svn:externals property to link them,
by setting the property URL to our own SVN 3rd party repository folder.

My svn paths are the following:

     https://svn.mysite.org/svn/trunk/myproject/extern
     https://svn.mysite.org/svn/vendor/3rdParty

On the '.../myProject/extern' folder above I have defined the following
property on my local working copy:

> cd ./myProject
>svn propset svn:externals '3rdParty
https://svn.mysite.org/svn/vendor/3rdParty' extern

What I thought this would do on checkout (or update) is create a folder
called '.../myProject/extern/3rdParty' and place in it everything from
'.../vendor/3rdParty'. So I'm either doing it wrong or it isn't
supported, because I get the following error:

     Fetching external item into 'extern/3rdParty'
     svn: Working copy 'extern/3rdParty' locked
     svn: run 'svn cleanup' to remove locks (type 'svn help cleanup'
for details)

All attempts at running svn cleanup succeed, but don't change the
result. Should this be possible and if so what could I be doing wrong?

TIA!!!!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 2 21:53:41 2005

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.