开发者

Large svn external

开发者 https://www.devze.com 2022-12-26 15:33 出处:网络
I have a project which uses a large library residing in its own repository. Using: TortoiseSVN, the server is running an enterprise edition of VisualSVN

I have a project which uses a large library residing in its own repository.

Using: TortoiseSVN, the server is running an enterprise edition of VisualSVN

The project itself has the "standard" structure:

  • trunk
  • tags
  • branches

In each branch, tag, and trunk is the librar开发者_JS百科y, set as an external (svn:external property). If I get the entire tree, I get the library several times, which is just getting too ridiculously repetitive.

Is there a recommended structure for this? Or perhaps a way not to get all externals (because other externals are much smaller, easier to manipulate)?


The TortoiseSVN help has an appendix on including a common subproject. If the library isn't likely to change, I think using a relative location (the third option listed) is probably the best.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号