iPhone 项目的 Mercurial 分步指南？
我正在寻找 iPhone 项目的分步 Mercurial 指南。请假设：
hg已经安装- 观众对命令行操作感到满意
- 一切都在 OS X
作为新手，我特别感兴趣的是：
- 应该排除哪些文件
- 如何排除上述文件
- 指南/建议命名构建
- 任何相关经验以与他人分享
请不要不要讨论 hg 比任何其他 SCS 更好/更差的地方。这是一个如何问题，而不是一个为什么问题。
谢谢！
I am looking for a step-by-step Mercurial guide for iPhone projects. Please assume:
hgalready installed- the audience is comfortable with command line operations
- everything is on OS X
As a newbie, I am particular interested in:
- what files should be excluded
- how to exclude above files
- guideline/suggestion of naming builds
- any relevant experience to share with
Please do not discuss how hg is better/worse than any other SCS. This is a how-to question, not a why question.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
一个适用于所有源代码控制系统的更通用的排除技巧是，将 Xcode 设置为使用远离源代码的共享构建目录确实很有用。我更喜欢使用 /Users/Shared/builds/ 但它可以去任何地方。好处是您无需费心从 hg 中排除构建产品，而且也可以方便地将它们从备份中排除。
您可以在 Xcode 首选项的“构建”下进行设置。
A more general exclusion tip that applies to all source-control systems is that it's really useful to set up Xcode to use a shared build directory somewhere away from the source code. I prefer to use /Users/Shared/builds/ but it could go anywhere. The nice thing is that you don't need to bother excluding build products from hg, and it makes it convenient to exclude them from backups as well.
You can set this up in Xcode's preferences, under "building".
您应该排除的文件是：
.DS_Store build *.mode1v3 *.pbxuser。您还可以始终忽略来自其他 SCS 的内容，例如.git和.svn。我还忽略了我的一些项目中的 .LSOverride ，因为我多次安装了开发人员工具（针对 SDK beta）并且有时想要覆盖标准启动服务行为。通过将这些文件列在工作目录根目录下的
.hgignore文件中，可以忽略这些文件。.hgignore文件必须手动创建。它通常置于版本控制之下，以便设置将通过推拉传播到其他存储库 [1]。Files you should exclude are:
.DS_Store build *.mode1v3 *.pbxuser. You can also always ignore stuff from other SCSs like.gitand.svn. I also ignore.LSOverridewhich is in some of my projects since I have multiple installs of the developer tools (for SDK betas) and sometimes want to override the standard launch service behavior.These files can be ignored by listing them in a
.hgignorefile in the root of the working directory. The.hgignorefile must be created manually. It is typically put under version control, so that the settings will propagate to other repositories with push and pull [1].