我可以使用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?

推荐答案

没有很好的方法仅使用水银来做到这一点.其他地方提到的森林扩展"引起了更多现今已修复的问题.大多数人只是使用大型仓库，并将所有组件都包含在仓库中，然后让其构建脚本下载并使用3rd party库-如果是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屋！