使用MySQL从.net - 许可的关注 [英] Using MySql From .Net - Licensing Concerns

问题描述

我工作的一个项目，并试图确定要使用的平台。现在，我的第一选择是使用ASP.Net MVC与MySQL数据库。我有这种担忧的是，MySQL的司机有GPL许可证。我创建了这个公司，因此它不能成为一个开源项目。这里有问题，我有：

1. 如果我使用MySQL的驱动，有一个GPL许可，我必须使整个应用程序的开放源代码？
2. 在没有任何人知道，有一个限制较少的许可证？
任何其他MySQL驱动程序
3. 在PostgreSQL有一个LGPL许可证，我相信应该没问题，但我无法找到有ASP.Net和PostgreSQL任何托管网站。任何人都知道任何便宜的托管计划（$ 10- $ 20 /月preferably），提供两个？

解决方案

使用MySQL库将GPL的code碱基。

如果你正在写的code为多个客户，您将有义务释放源$ C ​​$ C到你系统的客户。你有GPL没有义务打开源$ C ​​$ C到广大公众，你根本无法prevent别人这样做。

让我再说一遍，随着人们变得很不清楚这一点。在GPL责成你作为分发软件的发布源$ C ​​$ C只有你实际上已经发布了软件的二进制这些实体的实体。如果你跟我有关系的，我知道你的软件副本（理想情况下我已经弥补你为它），然后弗兰克显示，询问了该软件，你有没有义务给（或卖出，或任何东西）软件弗兰克。这不是一些猫出来的袋的事情。

弗兰克来找我，我可以给（销售，贸易）给他，你不能这样做阻止我，但你没有承诺自己分发软件，也不支持弗兰克。因为我很可能是轮胎企业，分发软件真的不是我的包，所以这是不可能的，我会发布一些公共档案code了。

如果该项目是一个客户，他们可能也有权源$ C ​​$ C，无论如何，所以在GPL在这种情况下可能是一个不是问题的问题。

只要您拥有著作权的code，你可以随时更改许可证在将来的版本。所以，如果你选择以后不再使用MySQL，你可以非GPL的下一个版本，并使用一些其他的许可，但你不能非GPL任何发布的软件。

有关定制，垂直软件，在GPL确实是一个不是问题的问题，因为大多数企业根本就不是在软件分销业务，并作为供应商你没有义务真正支持任何人，但你的实际客户，而不是任何人他们有可能给源$ C ​​$ C了。主要关注的是在商业秘密等。

大众市场的软件是一个不同的问题，当然。

I am working on a project and trying to determine what platform to use. Right now, my first choice would be to use ASP.Net MVC with a MySql database. My concern with this is that the MySql drivers have a GPL license. I am creating this for a company and therefore it can't be an open-source project. Here are the questions I have:

1. If I use the MySql drivers which have a GPL license, do I have to make the entire application open-source?
2. Does anybody know of any other MySql drivers that have a less restrictive license?
3. PostgreSql has a LGPL license which I believe should be ok but I can't find any hosting sites that have ASP.Net and PostgreSql. Anybody know of any cheap hosting plans ($10-$20/mo preferably) that offer both?

解决方案

Using the MySQL libraries will GPL your code base.

If you're writing the code for multiple customers, you will be obligated to release the source code to you system to THOSE customers. You have no obligation under the GPL to open the source code to the public at large, you simply can not prevent someone else from doing so.

Let me repeat that, as people get really unclear about this point. The GPL obligates you as the entity distributing the software to release the source code only to those entities you have actually released a binary of the software to. If you have a relationship with me, and I get a copy of your software (and ideally I have compensated you for it), and then Frank shows up asking for the software, you have NO obligation to give (or sell, or anything) the software to Frank. It's not some "Cat out of the bag" thing.

Frank could come to me, and I can give (sell, trade) it to him, and you can not stop me from doing so, but you have no commitment to distribute the software yourself, nor support Frank. Since I may well be in the Tire business, distributing software really isn't my bag, so it's unlikely that I'll be posting code up on some public archive.

If the project is for a single customer, they may well be entitled to the source code anyway, so the GPL in this case is probably a non-issue.

As long as you have copyright to the code, you can always change the license for a future release. So, if you choose to no longer use MySQL later, you can "un-GPL" the next release and use some other license, however you can not "un-GPL" any released software.

For custom, vertical software, the GPL is really a non-issue as most companies simply are not in the software distribution business, and as a vendor you're not obligated to actually support anyone but your actual customers, rather than anyone they might have given the source code too. The primary concern is over trade secrets etc.

Mass market software is a different issue, of course.

这篇关于使用MySQL从.net - 许可的关注的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！