I have the exact same problem here. Right now, I use a common
top-level "common" directory. And my fellow developers also refuse to
get the whole tree, leading to this problem.
Honestly what I'd like to see is a way to see the entire tree in
Subversion, "checkmark" certain directories that I want to check-out,
and have the "dependencies" automatically checked in their respective
directories as well, which may not be in descendent directories of the
selected ones. While part of this may be an issue for TortoiseSVN, I
believe setting up "dependency" properties in Subversion in some
standard way so that Subversion command-line will automatically
check-out the requested directories and their dependency directories,
while preserving the entire tree structure to keep the relative paths
within the projects working, would be great!
Maybe this is somehow already implemented. I haven't heard anything
to lead me to believe that it has been, though.
On Mon, 18 Oct 2004 09:38:29 +0200, Klimek Manuel <m.klimek@el-me.de> wrote:
> Hi,
>
> I checked the web and the mailing lists but surprisingly
> didn't find a reference that anybody had the same problem
> that I have now (which could mean it's trivial :-)
> I've got a big subversion tree containing multiple
> projects. Now because subversion isn't able to checkout
> only part of the directory structure without a lot of
> playing around, the developers just check out 'their'
> project subtree to work on.
> base/
> proj_A/
> common/
> header.h
> proj_B/
> common/
> header.h
> Now we've got that header.h which is common to multiple
> projects. As far as I understood the concepts of the
> subversion implementation it should be fairly easy
> to have common/ in one project be just a link to common/
> in the other project. But if I use 'svn cp', commits
> into one project won't be visible in the other project.
> If I use some toplevel common/ directory, the developers
> have to checkout the whole subeversion tree, which they
> refuse to do...
> Now of course I can create some post-commit hook to
> automagically delete the common/ directory and set
> the link to the new revision. I just thought that
> the concept of subversion should allow such a 'real link',
> and wondered if I missed some easy solution.
>
> Apart from that we find subversion to be a really fine
> solution for our projects :-)
>
> best regards,
> Manuel
>
> --
> Manuel Klimek
> EL-ME AG
> Phone: +49 8752 864 0
> Email : m.klimek@el-me.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
Andrew Arnott
Web Developer
Brigham Young University
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 18 18:00:51 2004