Large svn external
I have a project that uses a large library that is in its own repository.
Usage: TortoiseSVN, the server runs a corporate version of VisualSVN
The project itself has a "standard" structure:
- trunk
- tags
- branches
In each branch, the tag and trunk are a library, specified as external (svn: external property). If I get the whole tree, I get the library multiple times, which is just too funny repeating itself.
Is there a recommended framework for this? Or maybe there is a way not to get all external ones (because other external ones are much smaller, easier to manipulate)?
+2
a source to share
1 answer
The TortoiseSVN help has an application for including a generic subproject . If the library is unlikely to change, I think using relative location (third option) is probably the best.
+6
a source to share