嵌套的 svn 存储库 [英] Nested svn repositories

问题描述

我在存储库中有一个项目 A".但是在那个项目中，我使用了一个托管在 Google Code 上的库.我的问题是:有什么办法可以让库文件挂钩"到 Google Code SVN，同时我的项目在我的回购中(它是该库的父级)，所以我可以在我决定时将库文件提交到我的存储库中，那个外部项目修改可以吗?

I got a "Project A" in repository. But in that project I'm using a library, which is hosted on Google Code. There is my question: is there any way, to have that library files "hooked" to Google Code SVN, and simultaneously my project in my repo (it's parent to that library), so I can commit library files into my repository when I decide, that outer project revision is ok?

我尝试在库文件夹中进行检出，文件是从 Google 的代码存储库下载的.但是我那个案例无法将它们添加到我的存储库中 - 它们在添加"窗口中不可见.

I've tried to do checkout in the library folder, files were downloaded from Google's Code repository. But I that case wasn't able to add them to my repository - they weren't visible in "Add" window.

推荐答案

您可以使用 External 这将导致 SVN 在您检出存储库时检出最新版本的外部文件.

You can use an External which will causes SVN to checkout the latest version of the external files, when you checkout your repository.

来自上面的页面:

svn:externals 属性的便利之处在于，一旦它被设置在一个版本化目录上，所有签出该目录的工作副本的人都可以从 externals 定义中受益.换句话说，一旦有人努力定义那些嵌套的工作副本检出，其他人就不必费心了——Subversion 将在检出原始工作副本时，也检出外部工作副本.

The convenience of the svn:externals property is that once it is set on a versioned directory, everyone who checks out a working copy with that directory also gets the benefit of the externals definition. In other words, once one person has made the effort to define those nested working copy checkouts, no one else has to bother—Subversion will, upon checkout of the original working copy, also checkout the external working copies.

这篇关于嵌套的 svn 存储库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！