我可以使用 mercurial 模拟 svn:externals 吗? [英] Can I emulate svn:externals using mercurial?

问题描述

我们正在考虑从 SVN 迁移到 Mercurial，但遇到了绊脚石.

We are considering a move from SVN to Mercurial, and have encountered a stumbling block.

我们目前使用 svn:externals 自动将一组通用库拉入工作目录.我在 Mercurial 中找不到此类支持.

We currently use svn:externals to automatically pull a common set of libraries into the working directory. I can't find support for anything like this in Mercurial.

有没有办法使用 Mercurial 自动执行此操作，或者我是否需要在构建过程中伪造它?

Is there a way to do this automatically with Mercurial, or do I need to fake it as part of my build process?

推荐答案

仅使用 mercurial 没有好的方法.其他地方提到的森林扩展会导致比现在修复更多的问题.大多数人只是使用一个大型存储库并将他们所有的组件都包含在存储库中，然后下载他们的构建脚本并使用 3rd 方库——如果他们是 Java 负责人，则使用 maven.

There's no good way to do it using mercurial only. The Forest Extension mentioned elsewhere causes more problems that in fixes nowadays. Most folks just use a large repo and include all their components in the repo and then have their build scripts download and use 3rd party libraries -- using maven if they're Java-heads.

简短的回答在你的构建过程中伪造它".

Short answer "fake it in your build process".

更新:

在 Mercurial 1.3 中添加了一个新的子存储库功能.它就像旧的森林扩展，但作为所有新代码开始.

In Mercurial 1.3 a new sub repos feature was added. it's like the old forest extension, but started as all new code.

Subrepos 被视为不得已的功能".

这篇关于我可以使用 mercurial 模拟 svn:externals 吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！