On Wed, Aug 30, 2006 at 02:54:50PM -0500, Johnathan Gifford wrote:
> As Blair point out the other day, have you looked at the svn:externals
> property?
>
> >From what you are describing, this will work exactly as your expecting,
> but with one advantage. Your letting Subversion handle the whole
> thing.
Nope, that's not what I am looking for. I am using svn:externals
already somewhere else, so I do know it and have some experience with it.
Problems of svn:externals :
- with svn:externals you need to give a full URL, and thus have to
enforce a particular access method. I do access my repository
through different methods, and SSL tunnels, so the front part of the
URL differs from time to time, e.g. tunneling
svn://localhost:xxxx/... with different ports at xxxx. svn:externals
does not work with this.
- svn:externals works only for a complete directory, but not for a
single file.
I have configuration directories with several files, where some need
to be shared and some not. Can't build that with svn:externals
- svn commit does not work on svn:externals directories. You'd have to
manually step into every single subdirectory and commit manually.
Error prone.
regards
Hadmut
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 23:11:14 2006