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

RE: Externals for a single file - usage?

From: Bob Archer <bob.archer_at_amsi.com>
Date: Thu, 2 Apr 2009 11:19:16 -0400

> I just don't understand this at all. I have a working copy of my
project checked out, I've also added the bin folder in my web project
into svn and it still doesn't work. Am I supposed to have a separate
checkout of my library on my machine and then put the url to *that* as
the path to the external? Surely the problem with that is that the path
on my machine will be different to the path needed for my co-workers and
we'll keep overwriting each others external properties when we check in?

 

Yes, you need the file you are referring to in the external to be in the
checked out working copy.

 

Here is what I did.

 

I have a working copy with:

 

ProjectName/Build/ccnetproject.xml

 

I want that file to be available at:

 

ProjectName/Product/Install

 

So, I add the following property to the Install folder:

 

svn:externals ../../Build/ccnetproject.xml ccnetproject.xml

 

Now, when I update the "Installs" folder the ccnetproject.xml file is
put into the installs folder as a versioned file. So,
ProjectName/Build/ccnetproject.xml needs to be checked out in the WC
where my file external is.

 

So, you can't refer to a file that is only in the repository. Why this
is? I know not. Seems like a limitation that would be nice if it were
lifted. But, it is there in this version.

 

I tried to create a file external that pointed to a file in a directory
external, but that didn't work.

 

So, HTH,

BOb

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1520124

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-02 17:21:46 CEST

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.