SteveKing wrote:
>> I see. But you could create a separate repository for each of your
>> projects (which is recommended anyway).
I think I have a much better reason..
Often times, different projects have different project managers.
Which means that any policy regarding repository access, structure,
backup and what not is maintained by that project manager, usually
complying to the wishes of his particular team of developers. Much
easier not to step anyone on his/her toes with separate repos.
C. Michael Pilato wrote:
> svn:externals is a half-brained hack, which only works on whole
> directories (not files), and doesn't permit you to actually make (and
> keep) modifications to the code you've pulled in via that mechanisms.
It's an extremely useful hack though, which has got other uses than
the one you outline above.
For example, we use it for our web codebase.
We maintain 3 different web sites which share code.
All the code resides in the same repo but in different folders,
so we use 'svn:externals' to have it put in all the WC's correctly.
There are problems however.
These are the major ones:
- Commits to the repo becomes non-atomic :-(.
- After tagging the code with 'svn cp', the shared files are not
pinned at their current revision - they keep "updating inside the
tag".
- You *have* to specify a server name in every external reference in
the repo. When the source server changes FQDN or some such, those all
needlessly become invalid.
Futhermore, a minor point (IMHO):
- A few people have complained about not being able to tell TSVN to
disallow commits to shared ('svn:external'ed) code.
Personally, I think they're just stupid, but the need is apparently
there - there's an entry in the TSVN FAQ which provides a workaround.
The workaround is to checkout (or was it export?) the shared files
separately and then copy that WC/folder into one's project WC.
Or just hack the entries file and remove the dir entry.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu May 26 15:07:33 2005