Mercurial 代码库的包装器目录
我们的团队正在迁移到 Mercurial（从 SVN）。我们中没有人有太多设置用于推/拉的中央服务器的经验。
在 Subversion 中，我们的顶级目录当前是“codebase”，在其中我们有所有常见的嫌疑...
codebase <- subversion root
- .svn
- src
- docs
- etc.
对于我们的中央 hg 服务器，我们设置了一个顶级包装文件夹，它是 hg 存储库，然后在其中，我们放置“codebase”文件夹。因此，Mercurial 目录结构如下所示...
dev <- mercurial root
- .hg
- .hgignore
- codebase
- src
- docs
- etc.
请注意，新的 hg 服务器将不会保留任何 .svn 工件。包装文件夹的目的不是“包装” svn 存储库。该代码已从原始 svn 存储库中导出，只是一个“新”hg 代码库。
我看不出使用顶级包装文件夹有任何优势，但团队认为这是一个好主意。我仍然看不出其中的原因。
这里有人可以提供一些指导来解释为什么“包装器”文件夹可能是一个好主意或坏主意吗？对我来说，这似乎是一个不必要的嵌套，这让事情变得更令人恼火（特别是在命令行中）。
但也许有一些我不明白的优势？
谢谢你！
-加里
Our team is moving to mercurial (from SVN). None of us has a lot of experience setting up a central server for push/pulls.
In subversion our top-level directory is currently "codebase" and within it we have all the usual suspects...
codebase <- subversion root
- .svn
- src
- docs
- etc.
For our central hg server, we've setup a top-level wrapper folder that's the hg repository and then, within that, we put the "codebase" folder. So the Mercurial dir structure looks like this...
dev <- mercurial root
- .hg
- .hgignore
- codebase
- src
- docs
- etc.
Note the the new hg server will not be preserving any of the .svn artifacts. The intent with the wrapper folder isn't to "wrap" an svn repo. The code has been exported out of the original svn repo and is just a "new" hg codebase.
I can't see any advantage to using the top-level wrapper folder but the team has a soft-opinion that its a good idea. I still can't see the reason for it.
Can anybody here provide some guidance on why the "wrapper" folder might be a good or bad idea? To me it just seems like an unnecessary nesting that makes things a tiny bit more irritating (from the command-line particularly).
But maybe there's some advantage I'm just not understanding?
Thank you!
-Gary
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为包装
codebase的唯一优点是您可以从dev执行hg命令。如果您将文件转储到与代码库相同的级别，那么这可能是值得的。否则，对我来说，这看起来像是浪费一个目录。The only advantage I see to wrapping
codebaseis that you can do hg commands fromdev. If you dump files at the same level ascodebase, that might be worth while. Otherwise, it looks like a waste of a directory to me.