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

RE: Can I "graft" one project's working directory beneath another?

From: Dale Worley <dworley_at_pingtel.com>
Date: 2004-11-08 20:04:42 CET

What you did is correct as far as it goes. The library directory was marked
'?' since it is not a specified component of its parent directory.

But what you really want to be doing, I think, is to have the project-a
contain an "external link" to the library directory. That way, when you
check out project-a, your client also checks out library as the .../library
subdirectory of your working directory. Your client then conspires to make
the subdirectory largely act as an integral component of project-a.

However, when you want to make a tag of project-a and simultaneously make a
tag of library, things are messier, because the "svn copy" operation doesn't
update external links -- the tagged copy of project-a will still point to
(implicitly include) the main of library.

The svncopy.pl script takes care of this fairly well, except that the
current version requires that the tagged copy of project-a and library live
in sibling directories.

I'm working on revisions to svncopy.pl that allow you to specify
independently the destinations of the copies of the different components.

In regard to checking in changes in project-a/library and then checking them
out in project-b/library, that will work without any special arrangements.


-----Original Message-----
From: jhw@lmi.net [mailto:jhw@lmi.net]

What I'm really hoping to get out of this is stuff like this:

  me:~ > svn cp project-a repo:/project-a/tags/tag0001

..and have this do the nice recursive thing of including an
*simultaneous* tag of the library trunk inside the tag of

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 8 22:23:20 2004

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.