RE: Re: "sharing" and svn:externals

> -----Original Message-----
> From: Tommy Knowlton [mailto:Tommy@KE4KUG.net]
>
> If all your clients are UNIX, you may be able to take
> advantage of svn's built-in support for symlinks... just make
> the client's lib reference be a symlink to the relative path
> of the provider's working copy. This also assumes that it's
> reasonable to have provider (bin) wc's checked out everywhere
> you're using the client wc.
>
> hth,
> \Tommy
>
You know, I thought to myself before hitting send, "self, maybe you
should specify that this is on Windows with C# applications". I ignored
myself. Bad call :)

This is a Windows environment with the whole .NET "solution/project"
layout using "references".

Additionally, I think your idea just gives me the same problem with a
different implementation, so I'll clarify my intension a bit. In my
workspace, I want to see this:

MyProject
  |___libs
          |__lib1.dll
          |__lib2.dll
          |__lib3.dll
          |__lib3.pdb <-- debug library information if I'm looking at
debug environment.

Where lib1-3 are each in Subversion in separate
folders/projects/branches that belong to their own projects and are in
one and only one place. Per client project, I would be able to mix and
match the assemblies I need for that solution.

> On Oct 15, 2007, at 10:04 AM, Bicking, David (HHoldings, IT) wrote:
>
> > I'm defining project layout scenarios, and I hit upon a
> question. I'm
> > considering a structure in which shared, reusable library
> binaries are
> > stored in SVN in its own folder, and I want to have other projects
> > reference these libraries. I also want to be able to put these
 <snip>

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org