svn-externals

Can I emulate svn:externals using mercurial?

由 淺唱寂寞╮ 提交于 2019-11-27 10:05:54
问题 We are considering a move from SVN to Mercurial, and have encountered a stumbling block. 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. Is there a way to do this automatically with Mercurial, or do I need to fake it as part of my build process? 回答1: There's no good way to do it using mercurial only. The Forest Extension mentioned elsewhere causes more problems that in fixes

Are subversion externals an antipattern?

由 血红的双手。 提交于 2019-11-26 23:21:07
Subversion lets you embed working copies of other repositories using externals , allowing easy version control of third-party library software in your project. While these seem ideal for the reuse of libraries and version control of vendor software , they aren't without their critics : Please don't use Subversion externals (or similar in other tools), they are an anti-pattern and, therefore, unnecessary Are there hidden risks in using externals? Please explain why they would they be considered an antipattern. Rob Williams I am the author of the quote in the question, which came from a previous

Can we set a single file as external in Subversion?

由 白昼怎懂夜的黑 提交于 2019-11-26 23:11:57
问题 Can we set a single file as external in Subversion? 回答1: Yes, it's possible with svn 1.6. It's documented in the nightly build version of the svn book. But even though file externals are working, you should only do it with text files (for now) because binary files won't work correctly as file externals. 回答2: As mentioned in the first answer, SVN Externals are documented in Chapter 3 of the SVN Book, and quite a few syntax examples are given there. In addition, this note is given: "Because the

Are subversion externals an antipattern?

由 耗尽温柔 提交于 2019-11-26 12:19:54
问题 Subversion lets you embed working copies of other repositories using externals, allowing easy version control of third-party library software in your project. While these seem ideal for the reuse of libraries and version control of vendor software, they aren\'t without their critics: Please don\'t use Subversion externals (or similar in other tools), they are an anti-pattern and, therefore, unnecessary Are there hidden risks in using externals? Please explain why they would they be considered

Why are git submodules incompatible with svn externals?

由 蹲街弑〆低调 提交于 2019-11-26 03:25:08
问题 There are lots of webpages out there suggesting hackish ways to make svn externals look like git submodules. I have read some accounts of what the difference is, but this doesn\'t seem very fundamental: Git submodules link to a particular commit in another project\'s repository, while svn:externals always fetch the latest revision. Why does this difference make them so fundamentally incompatible? Isn\'t there a reasonable default we can assume, such as that most svn:externals point to tags

Why are git submodules incompatible with svn externals?

由 空扰寡人 提交于 2019-11-25 22:40:20
There are lots of webpages out there suggesting hackish ways to make svn externals look like git submodules . I have read some accounts of what the difference is, but this doesn't seem very fundamental: Git submodules link to a particular commit in another project's repository, while svn:externals always fetch the latest revision. Why does this difference make them so fundamentally incompatible? Isn't there a reasonable default we can assume, such as that most svn:externals point to tags that never move? VonC The fundamental difference is the composition rule . In a true component-based
订阅 svn-externals