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
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
> libraries into a "libs" folder in these client projects.
> Unfortunately,
> I don't know how to do that in SVN. Here's a sample repository
> structure for such a library.
>
> Lib1
> |___binaries
> | |__debug
> | |__release
> | |__tags
> | |__Release v1.1.0
> |
> |___branches
> |-___tags
> |___trunk
>
>
> I could use svn:externals, except that I have to specify it at the
> folder level, so I might name the definition "lib1_bin" and it would
> appear in my client project, and I could set my references. This
> falls
> apart if I have a lib2, lib3, etc., and want to drop those files into
> one "lib" folder on a client project.
>
> Does anyone here have a suggestion? Can I do what I want with SVN
> without creating a potentially complex series of copies? The key
> for me
> is simplicity in repository layout and maintenance.
>
> --
> David Bicking
>
>
> **********************************************************************
> ***
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 15 18:29:12 2007