2005/10/1, Thomas Hruska <thruska@cubiclesoft.com>:
> I've read it and Appendix B. It didn't answer my question. There are
> several methods discussed and none of them are indicated as the
> "favored" or "preferred" method. And none really address my scenario.
> I just tried the svn:externals approach and that creates a copy of
> CoreLibrary in each project's directory. CoreLibrary is huge and I'd
> prefer not having it duplicated everywhere, but what SVN is doing makes
> _some_ sense at least for previous versions. For the current version,
> however, it doesn't make much sense to have the same code duplicated
> everywhere. I work on multiple projects and applications at any given
> time that all rely on the CoreLibrary project. I don't want to have to
> commit every change I make just to synchronize multiple copies. The
> problem could be solved with allowing relative directories via '..', but
> unfortunately svn:externals doesn't allow that.
Perhaps you need to re-think how you're using the "CoreLibrary". Can't
you just have a single copy of each version you need and reference it
as a dependency from your various projects?
It sounds like you want the equivalent of a symbolic link to
CoreLibrary from your projects, which you theoretically can do with a
NTFS junction, but there are any number of reasons why this isn't
necessarily a good idea. I have no idea about how well Subversion
itself will work with junctions (I suspect it'll be fine as long as
you don't have a infinite nesting problem), but since most Windows
functionality is not aware of them - they're treated as completely
separate directories, so if you're not being careful you can end up
deleting stuff that you don't intend to.
-Daniel
Received on Sun Oct 2 03:02:08 2005