On Thu, Jan 7, 2010 at 17:22, Bryce Bingham <bryce.bingham_at_gmail.com> wrote:
> Hey all,
>
> My problem is the following:
>
> I have 2 repositories, one for a library and one for a product that
> uses the library. That is:
>
> LIBRARY = source code for building a particular module
> PRODUCT1 = source code for building a specific product, composed of
> several modules
>
> During development, we've maintained a separate LIBRARY as a submodule
> of PRODUCT 1. That is, our repository looks like:
>
> MAIN BRANCH
> |
> |
> +------------------------------+----------- . . .
> | |
> | + PRODUCT1
> + LIBRARY |
> + OTHER MODULES
> + LOCAL LIBRARY
>
> Now that PRODUCT1 is fleshed out, we'd like to merge the changes in
> PRODUCT1/LOCAL LIBRARY into MAIN BRANCH/LIBRARY. The idea is that
> multiple products can all use this same LIBRARY.
>
> My question: Is there a simple way to organize/automate SVN so that we
> can check out the pertinent repositories with one checkout?
>
> That is, a developer does an SVN Checkout of PRODUCT1. They therefore
> check out:
> + PRODUCT1
> + PRODUCT1/OTHER MODULES
> + MAIN BRANCH/LIBRARY
>
> If another developer checks out PRODUCT2, they will similarly check
> out all their files plus MAIN BRANCH/LIBRARY.
>
> We'd like to avoid forcing the developer to do 2 checkouts (1 for
> product, 1 for library). I was curious as to whether SVN had an
> ability to use a symbolic link to other modules not in current branch.
Subversion supports symlinks, but not on Windows because until Vista,
Windows didn't do symlinks.
You're looking for svn:externals.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2435653
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-08 02:21:01 CET