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

Re: SVN:Externals

From: Res Pons <pons32_at_hotmail.com>
Date: 2006-10-20 02:24:02 CEST

Great, thank you for all your help and the thorough explanation, it makes
more sense now.

----Original Message Follows----
From: Ryan Schmidt <subversion-2006d@ryandesign.com>
To: Res Pons <pons32@hotmail.com>
CC: users@subversion.tigris.org
Subject: Re: SVN:Externals
Date: Thu, 19 Oct 2006 18:07:03 -0500

On Oct 19, 2006, at 13:26, Res Pons wrote:

>I find svn:externals extremely difficult to use and comprehend especially
>when there're very few examples provided in the manual. I have our SVN
>repository on a RHEL 4 Enterprise Linux box along with WinXP clients. I
>browse to my working folder and do svn propget svn:externals '.' (dot for
>here) and I get tons of errors.

Such as?

>I tried to set the externals a while back and now it has locked up the
>folders and SVN Clean Up won't work either. How can I find out where the
>externals are set and undo them? Could someone help me please, many

You can recursively get all properties on all items in your working copy:

cd working-copy
svn proplist -v -R . | less

Now search through that for occurrences of "svn:externals"

>Here's a list of errors:
>1- svn: Explicit target required ('interact' interpreted as prop value)

You have executed an invalid command in attempting to set the svn:externals
property; therefore, no property was set. Show us the command you attempted
to execute and we'll show you what you need to change.

I'll give you an example though. Suppose you have a working copy, and it
contains a directory "lib", and inside lib you want to pull in various
external libraries from elsewhere in your repository. Suppose your
repository root is at http://www.example.org/svn/ .

cd working-copy/lib
svn propedit svn:externals .

Note the dot (".") at the end to indicate that you want to set this
property on the directory you're in right now. "svn propedit" will bring up
your preferred editor where you should enter one line per external library
that you want to bring in. Each line has two fields, separated by a tab.
The first field is the name of the directory that you want to have created
in your local working copy. After the tab, the second field is the URL to
the repository for the original item. So if you have, say,
vendor/prototype/1.4.0 and vendor/smarty/2.6.14 in your repository and want
to bring these into your lib directory, then the svn:externals property
might read:

prototype http://www.example.org/svn/vendor/prototype/1.4.0
smarty http://www.example.org/svn/vendor/smarty/2.6.14

>2- svn: This client is too old to work with working copy 'pix'; please get
>a newer
>Subversion client

That has nothing to do with any of your svn:externals troubles. You have
previously used a Subversion 1.4 client on this working copy, and are now
trying to use a pre-1.4 client with the working copy. Use only Subversion
1.4 clients with this working copy from now on.

Try Search Survival Kits: Fix up your home and better handle your cash with
Live Search!

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 20 02:24:42 2006

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.