Mercurial hgsubversion 扩展使 SVNExternals 的行为类似于 Hg 子存储库
此问题与将 Mercurial hgsubversion 扩展与 SVN 外部一起使用。但是，与执行 hg svn update 相关的问题的第二部分尚未得到解答。
是否可以将您从中提取的 Subversion 存储库中的 SVN 外部文件转换为 Mercurial 子存储库？
This question is related to Using the Mercurial hgsubversion extension with SVN Externals. However, the second part of the question relating to doing a hg svn update has not been answered.
Is it possible to get the SVN externals in the subversion repository that you pull from to be converted into a Mercurial sub repository?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
不要尝试通过 Mercurial（或任何 SCM）来管理依赖项，而是尝试使用依赖项管理工具，例如 Apache Ivy。
更多详细信息请参阅 Hg 子存储库依赖项
编辑：类似的答案略有不同的旋转 最佳实践用于 Mercurial 和 Eclipse 的项目功能子模块？
Instead of trying to manage your dependencies via Mercurial (or with any SCM for that matter), try using a dependency management tool instead, such as Apache Ivy.
More details in answer to Hg sub-repository dependencies
EDIT: Similar answer with a slightly different spin at Best Practices for Project Feature Sub-Modules with Mercurial and Eclipse?
我们目前在 hgsubversion 中不支持自动将外部引用转换为 hg 存储库。作为功能贡献，我对此持开放态度，但需要对其进行充分测试。
We don't currently have any support in hgsubversion for automatically turning externals references into hg repositories. I'd be somewhat open to that as a feature contribution, but it'd need to be well tested.
我发现原来的问题还包含您遇到的外部问题的部分答案。但是，您是否可以将配置的外部文件视为常规 Subversion 存储库文件夹，而使用
hgsubversion来更新 Mercurial 子存储库？这显然不允许自动处理外部，但似乎是解决该问题的一个半途而废的解决方案（至少在
hgsubversion中修复不使用标准 Subversion 存储库配置时的外部问题之前）。从 Mercurial 1.5 开始，子存储库功能似乎还可以支持子存储库的其他存储库类型，例如 Subversion。请参阅子存储库文档的第 2.1.1 节。I see that the original question also contains a partial answer to the externals problem you were having. However, could you just treat your configured externals as a regular Subversion repository folder and instead use
hgsubversionto update Mercurial Subrepositories?This obviously doesn't allow automatic handling of externals, but seems like a halfway decent solution to the problem (at least until the externals issue when not using the standard Subversion repository configuration is fixed in
hgsubversion). It also looks like since Mercurial 1.5, the Subrepository feature can support other repository types for the subrepository like Subversion. See section 2.1.1 of the Subrepositories documentation.