> - 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.
Change the external property as needed. Simple as a commit to the
repository directory your wanting to get. Better yet, standardize your
access protocol then you won't have to change those external properties
as much.
> - svn:externals works only for a complete directory, but not for a
> single file.
Argh... the whole 'need only' a file thing. Export has the same
'feature'. Yes, this can be a pain to deal with. Only suggestion I can
offer up is to change your directory structure to accommodate this
'feature' of Subversion. Yo' Subversion developers, if you're reading
this, this would be a very nice improvement for the externals and export
functionality!
> - svn commit does not work on svn:externals directories. You'd have
to
> manually step into every single subdirectory and commit manually.
> Error prone.
Actually, this does work in in Eclipse with the Subclipse plugin. I
can't verify that with the command line (never tried), but I know it
does work with Subclipse without errors.
---------------------------------------------------------------------
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:24:39 2006