Molle Bestefich wrote:
> 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.
Another (albeit minor) problem:
'svn log <URL>' doesn't show any log entries for the shared code.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu May 26 17:12:32 2005