Sure.
I think you could use the Externals to do that.
Using External you can add a subfolder (or simple files) into your
repository, and when you do an update or a checkout, everything will
just works.
Please, found the external topic on tortoise manual (and svn manual
too). You can define an external file or folder from your own
repositories or from others repositories. You need to configure a
property named "svn:externals". If you do that with tortoise, follow
these steps:
1) Right click on folder
2) Chose the svn properties
3) Add a new property named svn:externals
4) Add "^/trunk/Library Library" in the property values.
5) Save this property e "update" your work copy.
You can use some special characters to create relative references. For
example, ^/trunk/Library means the same repository; /svn/Library/
trunk/ means the same server but Library repository. And you can
define an external reference using any other protocols like https:
https://myserver/svn/Library/trunk/ means the svn server on
"myserver".
You can find out a lot about on tortoise and svn manual.
Rafael M. Heise
On 7 jan, 20:22, Bryce Bingham <bryce.bing..._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.
>
> Regards,
> Bryce Bingham
>
> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
>
> To unsubscribe from this discussion, e-mail: [users-unsubscr..._at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2435656
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-08 02:33:08 CET