需要存储库布局参考
我期待着一场关于 Subversion 存储库的战斗:目前我们有一个 Web 应用程序,它被签入为 3 个主要项目和 2 个报告项目(当我 6 个月前开始时),现在已达到 7 个项目,并且预计会进一步增长。
对我来说,显然这是不对,如果您想合理使用版本控制系统,编译后的可执行文件不能跨越版本控制边界。对单个功能进行一次签入是不可能的,这对我来说似乎很重要。
但当我试图解释这一点时,我感觉自己在挥手。有没有人有任何关于 Subversion 或一般情况的参考资料,阐述了这一原则并在其背后拥有一定的权威?我做了一些搜索,但没有找到我需要的东西。
I am anticipating a battle over Subversion repositories: currently we have a single web application that was checked in as 3 main projects and 2 reports projects (when I started 6 months ago), is now up to 7 projects, and is expected to grow further.
It is obvious to me that this is just not right, that a compiled executable cannot cross a version-control boundary if you want to make reasonable use of the version-control system. It's impossible to have a single checkin for a single feature, and that seems essential to me.
But I feel like I'm hand-waving when I try to explain this. Does anyone have any references, for Subversion or in general, that lays out this principle and has some authority behind it? I've done some searching and am just not coming up with what I need.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
Subversion 中有很多选项可以帮助您构建存储库。请参阅存储库布局的讨论 在文档中。
我通常会遵循以下规则:
==>您可以使用不同的存储库(但不是强制的)。
区别如下:
单个项目布局:
多项目布局:
主要区别如下:
作为参考,我只有引用的SVN红皮书,当然还有stackoverflow中的众多答案之一: Subversion Repository布局
There are a lot of options in Subversion how to structure your repository. See the discussion of repository layout in the documentation.
I would normally follow these rules:
==> You may use different repositories (but are not forced to.
The difference is the following:
Single project layout:
Multi project layout:
So the main differences are the following:
As a reference, I only have the quoted SVN red book, and of course one of the many answers in stackoverflow: Subversion Repository Layout