问题描述
出于各种原因，我正在将Mercurial用于个人用途，并将其用于某些分布式项目，以替代SVN.
I'm using Mercurial for personal use and am conteplating it for some distributed projects as an alternative to SVN for various reasons.
我对在独立项目中使用它感到很自在，可以看到各种共享选项，但是我还没有找到关于管理公共库的指南以类似于外部的方式包含在多个项目中在颠覆中.
I'm getting comfortable with using it for self contained projects and can see various options for sharing however I haven't yet found any guidance on managing common libraries to be included in multiple projects in a similar manner to that provided by externals in subversion.
最明显的共享代码块是错误处理和报告-我们希望这在所有项目中都几乎相同(其发展得相当不错).与每个解决方案一起构建的项目相比，还有更好的实用程序代码，控制库和类似内容，而不是作为编译类引入(特别是因为它确保它们保持最新状态，持续集成可帮助我们应对突破性变化)
The most obvious shared lump of code is error handling and reporting - we want this to be pretty much the same in all projects (its fairly well evolved). There is also utility code, control libraries and similar that we find better to have as projects built with each solution than to pull in as compiled classes (not least because it ensures they are kept up to date, continuous integration helps us address breaking changes).
想法(我讨厌开放式的问题，但我想知道别人在做什么(如果有的话).
Thoughts (I hate open ended questions, but I want to know what, if anything, others are doing).
推荐答案
Mercurial 1.3现在包括嵌套存储库支持，可用于表达依赖关系.另一个选择是让您的构建系统使用ivy或maven之类的东西来处理依赖项的下载和跟踪，尽管它们更侧重于提取编译的代码.
Mercurial 1.3 now includes nested repository support, which can be used to express dependencies. The other option is to let your build system handle the download and tracking of dependencies using something like ivy or maven though those are more focused on pulling down compiled code.
这篇关于Mercurial:如何管理通用/共享代码的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！