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

Re: Advice on handling common code

From: Ben Fritz <fritzophrenic_at_gmail.com>
Date: Mon, 14 Jan 2013 09:55:06 -0600

On Fri, Jan 11, 2013 at 12:44 PM, C M <cmanalyst66_at_gmail.com> wrote:
> Ben,
>
> Thanks for the offer to help. I set the "svn:externals" property on a
> directory via the TortoiseGUI. My expectation is to have that directory
> available to me in another location (in the same repo).
>
> Am I correct in thinking that? And if so, do I need to do something explicit
> to see the directory in the location where I want it?
>
> When setting the properties, for the URL field, I specified the path where I
> expect to directory to be available to me.

It sounds like you are trying to place an svn:externals definition on the
source directory you want to place somewhere else. This is wrong. You need to
set the svn:externals property on the destination directory where you want to
place a copy of the source directory.

For example, say you have two projects in a single repository, hosted at:

  http://example.com/svn

Your two projects have the following two URLs:

  http://example.com/svn/app_project/trunk
  http://example.com/svn/library_project/trunk

Now say that when you make a checkout of your app_project, you need to have a
copy of the library project in a "lib" folder. To accomplish this, in its
simplest form, you need to set the svn:externals property on the
app_project/trunk directory to:

  http://example.com/svn/library_project/trunk lib

This says:

  "When a user makes a checkout of the app_project/trunk directory, place a
  checkout of library_project/trunk into the 'lib' directory inside the working
  copy of app_project/trunk."

>
> This is the output when of the svn propget after I set the values. I am not
> clear on what to do or expect next.
>
> C:\>svn propget svn:externals svn://x.x.x.x/bopcs/trunk/system1/cpu
> svn://x.x.x./bopcs/trunk//system2 cpu
>

What this definition will do, is that every time you make a checkout of
svn://x.x.x.x/bopcs/trunk/system1/cpu, you will get a subdirectory in your
working copy also called cpu, which is a working copy of
svn://x.x.x./bopcs/trunk//system2. I am not clear whether this is what you want
or not, but from your first few paragraphs I think it is not.

Please read the following for more information about what svn:externals do, the
syntax for using them, and usage examples:
http://svnbook.red-bean.com/en/1.7/svn.advanced.externals.html

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3043360

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-14 16:55:31 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.