svn update does indeed work recursively down the tree, but commit does
not.
exmaple:
proja
\-- proja_random.txt
\-- external:projb
\-- projb_random.txt
svn update and status will both delve in to projb when excecuted from
the top directory.
But commit will only commit proja, leaving projb still uncommitted.
A small script to run "status" and grab all the lines marked with X
will produce a list of all your externals if you wanted to make a
super-commit thing, keep in mind, you'll have do do a separate commit
per repo rather than a single atomic transaction spanning all the
repositories.
On Sep 10, 2004, at 7:04 AM, Lee Merrill wrote:
> You can actually share files across multiple projects by using the
> "svn:externals" property, but "svn commit" and "svn update" (and some
> other commands) do not follow the links to the shared files, which
> makes it possible to do an inconsistent update/commit/etc. So wrapper
> scripts would probably be needed. The "-r" option should probably also
> be used if "svn:externals" is used, so that the correct, matching
> version of the shared files is retrieved. But if you change the shared
> files, then you also have to change the "-r" option in all the
> directories that reference them, but that's easier than changing
> copies of all the shared files in every project.
>
> Lee
>
>>> From what I can tell, Subversion does not currently let someone
>>> share a file across multiple projects.
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 10 20:35:48 2004