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

Re: Tree-internal real links

From: Andrew Arnott <andrewarnott_at_gmail.com>
Date: 2004-10-19 05:08:07 CEST

> What about this:
>
> Repository:
> /trunk/common
> /trunk/resources
> /trunk/tools
> /trunk/projects
> /trunk/projects/calc
> /trunk/projects/note
>
> /SingleProjCO/calc/projects/calc <where calc is an svn::externals to /trunk/projects/calc
> /SingleProjCO/calc/common <where common is an svn::externals to /trunk/common
> /SingleProjCO/calc/resources <where resources is an svn::externals to /trunk/common
> /SingleProjCO/calc/tools <where tools is an svn::externals to /trunk/common

That looks like it will work. Thanks for the tip. I gather then that
in the working copy, each project will have its own copy of the
libraries that many projects share. While these library sources will
be linked together in the repository, they will need to be
independently (and explicitly) committed and updated. Also, given
this configuration, I gather that when compiling I should reference
the libraries within the project rather than the libraries that are
siblings to the project.

I'm very new at organizing these things. Is this the typical way of
doing it then?

Thanks again for the tips.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 19 05:08:45 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.