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
Received on Mon Oct 18 17:50:21 2004