在 SVN 或其他版本控制系统中复制 Sourcesafe 的链接能力? [英] Replicating Sourcesafe's link ablity in SVN or other version control systems?

问题描述

目前，我的团队使用 Visual Sourcesafe，并且非常熟悉 GUI 的第一手可怕程度，并且听说过互联网上的哑巴说它是多么不可靠，我一直在努力推动转向 SVN.

Currently my team uses Visual Sourcesafe, and being very familiar with how horrible the GUI is first hand and having heard the internet mummer about how unreliable it is, I've been trying to push a move to SVN.

今天我和经理谈论了他支持的最终移动，他问是否可以在 SVN 中创建源安全样式链接.对于不熟悉 sourcesafe 的人来说，链接在概念上与 Linux 下的文件链接相同.我们使用它们来链接项目之间的共享代码/库.我解释说无法使用 SVN 创建链接，他提出这可能是迁移中的一个主要症结点.

Today I was talking to manager about the eventual move, which he supports, and he asked if it was possible to create sourcesafe style links in SVN. Links, for people not familiar with sourcesafe, work the same conceptually as file links under Linux. We use them to link shared code/libraries between projects. I explained that there was no way to create links using SVN, and he brought up that that may be a major sticking point in the migration.

我告诉他，在我的本地 SVN(我一直在简化我的开发，只在 sourcesafe 中定期检查)中，我将共享代码/库放在一个位置，并将 ANT 引用到该位置.但是，我感觉他对这个解决方案并没有留下深刻印象，因为它增加了 ANT 任务的复杂性.就我个人而言，我认为值得拥有一个稍微复杂一些的 ANT 脚本，而不是在源代码管理中拥有一堆链接文件，但这确实是您订阅哪种范式的问题.

I told him that in my local SVN (which I keep to ease my development, checking only periodically in sourcesafe), I place shared code/libraries in one location, and refer ANT to that location. However, I got the sense that he wasn't hugely impressed by this solution, as it adds complexity to ANT tasks. Personally I think it's worth having a slightly more complex ANT script over having a bunch of link files in source control, but it really a question of which paradigm you subscribe to.

我很好奇开发人员是如何解决这个限制的，是否有像 Git 和 Mercurial 这样的较新的源代码控制系统支持链接?

I am curious about how developers at large work around this limitation, and do newer source control systems like Git and Mercurial support links?

推荐答案

查看 svn:externals 属性.

Look into svn:externals properties.

这篇关于在 SVN 或其他版本控制系统中复制 Sourcesafe 的链接能力?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！