svn-externals 与自己的 svn-externals : how to recursively checkout?

Question

所以我使用 svn:externals 来检查一个外部仓库。外部仓库有自己的 svn-externals 设置。

现在，当更新我的项目的工作副本时，来自外部存储库的文件正在更新，但它的外部文件没有。该行为是否符合设计，是否可以扩展以更新外部依赖项？

Answer 1

从 Subversion1.5 开始支持递归结账，如 thread illustrates .
"Version Control with Subversion" book确实提到 svn checkout , svn update , svn switch , 和 svn export命令能够在外部存储库中递归，但是:

如果为特定修订设置了外部，则不会有任何“update” ' 将更改其中的任何文件，即使外部存储库有新的修订。

更新必须始终从父存储库启动，而不是直接从子存储库启动:

Be careful, though, that you don't inadvertently modify your external working copy in subtle ways that cause problems.
For example, while an externals definition might specify that the external working copy should be held at a particular revision number, if you run svn update directly on the external working copy, Subversion will oblige, and now your external working copy is out of sync with its declaration in the primary working copy.

所以也许这两种情况之一适用于这里。

OP Carsten报告:

It is actually working now.

I had set the externals prop on the root node of the external project (lets say project 'lib').
In my concrete project (project 'A'), the external was defined on a sub-folder of 'lib' (ie. myLocalFolder > lib/someFolder).
That seems to be the reason for subversion not recursing into lib's externals; only looked inside 'someFolder', didn't find external defs there, so it didn't checkout someFolder/externalLib.
Now, in 'lib' I changed externals definitions so that they are defined inside the folder that I refer to in 'A'; works like a charm now!