将TortoiseSVN与开发人员许可文件一起使用 [英] Using TortoiseSVN with developer licence files

问题描述

大家好，



我有兴趣了解包含项目的存储库中的最佳实践，该项目需要多个独立的开发人员许可文件才能构建和发布解决方案。项目中使用的组件/工具需要许可证文件（* .licx）（我不是指产品本身）。



我们有一个几个开发人员都拥有自己的许可证文件。如果这些许可证需要包含在解决方案中以便构建它，那么在更新/提交到存储库期间应如何处理这些许可证？



我正在使用TortoiseSVN。



谢谢，

解决方案

我会在一些不使用许可证文件的特殊开发版本上进行所有开发一点都不如果涉及程序集签名，您还可以使用延迟签名（ https://msdn.microsoft.com/en-us/library/t07a3dye%28v=vs.110%29.aspx ）。



在Subversion代码数据库中，您应该只存储源文件。许多开发人员很难理解他们的项目中的哪些文件是源文件，哪些不是 - 这是一个令人讨厌的问题，应该从一开始就解决，不允许发生。在某些情况下，可以添加一些在开发外部并且在技术上不是源文件的文件。这些文件也应该以某种方式存储，因为它们没有任何其他更原始的来源。因为它们不是开发过程的一部分，并且据说（几乎）永远不会改变并且不是创建开发版本的主题，我建议分别存储它们，包括许可文件。使用Subversion，我建议使用外部文件的机制： http://tortoisesvn.net/docs /nightly/TortoiseSVN_en/tsvn-dug-externals.html [ ^ ]。



首先引用的微软文章，关于延迟签名，涉及一个非常微妙的方面，可能与您的工作：开发团队不完全信任的技术，因此部分编程断言对所有或部分团队成员保密;本文介绍了以这种方式限制开发人员访问的技术之一。你必须自己决定，但我自己的意见是：在这方面相信开发人员，因为不相信他们会造成道德风险。修订控制和其他技术工具应该只能防止意外错误，例如无能的步骤，而不是窃取财产;开发人员应该基于道德原则和一些激励措施忠诚于他们的组织，而不是让人们戴上技术手铐。

-SA

Hi all,

I'm interested in learning what is considered best practise within a repository that contains a project that requires several independent developer licence files for building and publishing the solution. The licence files (*.licx) are needed for the components/tools used within the project (I don't mean for the product itself).

We have a couple of developers that all have their own licence files. If these licences need to be in included in the solution in order to build it how should they be handled during update/commits to the repository?

I am using TortoiseSVN.

Thanks,

解决方案

I would do all the development on some special development versions not using license files at all. If assembly signing is involved, you could also use delayed signing (https://msdn.microsoft.com/en-us/library/t07a3dye%28v=vs.110%29.aspx).

In the Subversion code database, you should store only the source files. Many developers poorly understand which files in their projects are source files and which are not — this is a nasty problem which should be solved from the very beginning and not allowed to happen. In some cases, some file which is external to development and is not technically a source file, can be added. Such files are also should be stored somehow, because there are no any other, "more original" source for them. As they are not part of the development process, and supposedly (almost) never change and are not subject of creating development versions, I would suggest to store them, including license files, separately. With Subversion, I would suggest using the mechanism of external files: http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-externals.html[^].

The Microsoft article referenced first, about delaying of signing, touches a very delicate aspect which may be related to your work: the technology where the development team is not fully trusted, so part of the programming asserts is kept in secret from all or some team members; the article describes one of the technologies limiting developers' access in this way. You have to decide on that by yourself, but my own opinion is: trust the developers in this respect, as not trusting them can create moral hazard. Revision control and other technical tools should only protect against accidental mistakes and, say, incompetent steps, not from stealing property; developers should be loyal to their organization based on moral principles and some incentives, not by keeping people in technical handcuffs.

—SA

这篇关于将TortoiseSVN与开发人员许可文件一起使用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！