关于GPL和专有软件 [英] About GPL and proprietary software

查看:85
本文介绍了关于GPL和专有软件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在软件许可方面,我不会感到非常自信。但是

有些情况我想让自己清楚。我对
特别感兴趣的是什么?GPL许可证何时成为限制性的?

比如说公司有专有的软件产品只有

适用于MySQL,没有其他数据库系统。以下情况是否合法?
合法?

1)该公司在专有许可下销售他的产品,并将其留给客户设置需要MySQL服务器。或者也许帮助客户在没有额外费用的情况下设置MySQL。

2)客户每月向该公司支付使用其专有费用的费用
$ b使用公司服务器中托管的MySQL的$ b软件。

3)该公司在CD上以专有许可证销售他的产品

,其中还包括MySQL作为免费奖金(含源代码)。


如果这些情况有效,那么MySQL的GPL许可证(或者任何其他软件的b * b)在何时成为真正的限制一个

的专有公司?


Kaarel

----------------- ----------(广播结束)---------------------------

提示9:如果您的

加入列的数据类型不匹配,计划员将忽略您选择索引扫描的愿望

I don''t feel very confident when it comes to software licenses. But
there are some cases I would like to make myself clear. What I am
particulary interested in is when does GPL license become restrictive?
For example say a company has a proprietary software product that only
works with MySQL and no other database system. Are the following cases
legal?
1) This company sells his product under proprietary license and leaves
it up to the client to set up required MySQL server. Or perhaps helps
the client with seting up MySQL with or without extra fee.
2) Clients pay monthly fee to this company for using their proprietary
software which uses MySQL hosted in the companys server.
3) This company sells his product under proprietary license on the CD
which also includes MySQL as free bonus (with source code).

If these cases are valid, then when does GPL license for MySQL (or any
other software in that matter) become truly restrictive for a
proprietary company?

Kaarel
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column''s datatypes do not match

推荐答案

Kaarel< ka **** @ future.ee>写道:


[...]
Kaarel <ka****@future.ee> writes:

[...]
如果这些情况有效,那么什么时候GPL许可MySQL(或任何其他软件对于
专有公司是否真的受到限制?
If these cases are valid, then when does GPL license for MySQL (or any
other software in that matter) become truly restrictive for a
proprietary company?




这既不是GNU也不是MySQL邮件列表。我建议你把问题带到其中一个地方,因为你会得到更好的答案。


-Doug


---------------------------(播出结束)------------ ---------------

提示1:订阅和取消订阅命令转到 ma ******* @ postgresql.org



This is neither a GNU nor a MySQL mailing list. I suggest you take
your question to one of those places, as you''ll get a better answer.

-Doug

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org


On Sun,2003-08-31 at 07:26 ,Kaarel写道:
On Sun, 2003-08-31 at 07:26, Kaarel wrote:
我对软件许可证感到不自信。但是有些情况我想让自己清楚。我特别感兴趣的是GPL许可证什么时候变得有限制?
例如,一家公司有一个专有的软件产品,它只能与MySQL一起使用,而不是其他数据库系统。以下情况是否合法?
1)该公司在专有许可下销售他的产品,并将其留给客户设置所需的MySQL服务器。或者也许帮助客户在没有额外费用的情况下设置MySQL。
2)客户每月向该公司支付费用,使用他们使用公司服务器中托管的MySQL的专有软件。
3)该公司在CD上以专有许可证销售他的产品
其中还包括MySQL作为免费奖金(带源代码)。

如果这些情况有效,那么当MySQL的GPL许可(或其他任何软件)是否真的对专有公司有限制?
I don''t feel very confident when it comes to software licenses. But
there are some cases I would like to make myself clear. What I am
particulary interested in is when does GPL license become restrictive?
For example say a company has a proprietary software product that only
works with MySQL and no other database system. Are the following cases
legal?
1) This company sells his product under proprietary license and leaves
it up to the client to set up required MySQL server. Or perhaps helps
the client with seting up MySQL with or without extra fee.
2) Clients pay monthly fee to this company for using their proprietary
software which uses MySQL hosted in the companys server.
3) This company sells his product under proprietary license on the CD
which also includes MySQL as free bonus (with source code).

If these cases are valid, then when does GPL license for MySQL (or any
other software in that matter) become truly restrictive for a
proprietary company?




为什么要问关于MySQL(一个GPL许可的产品),在一个
PostgreSQL(一个BSD许可的产品)邮件列表上????


是这样的可能:

IANAL,但根据我的理解

(1)专有的s / w动态链接到GPL共享库

没有破坏GPL。

(2)*静态*链接到GPL的专有软件。图书馆已经打破了GPL。

(3)专有的s / w说话到GPL s / w通过管道,网络

链接等,不会打破GPL。


据推测,PostgreSQL是BSD的原因之一行货是

以避免这样的问题。


-

------------ -------------------------------------------------- ---

Ron Johnson,Jr。 ro ******** ***@cox.net

美国路易斯安那州杰斐逊


弗拉基米尔普京4度

- -------------------------(播出结束)-------------------- -------

提示5:您查看了我们广泛的常见问题解答吗?

http://www.postgresql.org/docs/faqs/FAQ.html



Why are you asking about MySQL (a GPL-licensed product), on a
PostgreSQL (a BSD-licensed product) mailing list????

Be that as it may:
IANAL, but according to my understanding
(1) proprietary s/w that dynamically links to "GPL" shared libraries
has not broken the GPL.
(2) proprietary s/w that *statically* links to "GPL" libraries has
broken the GPL.
(3) proprietary s/w that "speaks" to "GPL" s/w via a pipe, network
link, etc., does not break the GPL.

Presumably, one of the reasons that PostgreSQL is BSD-licensed is
to avoid issues like this.

--
-----------------------------------------------------------------
Ron Johnson, Jr. ro***********@cox.net
Jefferson, LA USA

4 degrees from Vladimir Putin
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html


Kaarel写道:
Kaarel writes:
我对软件许可证感到不自信。但是有些情况我想让自己清楚。我特别感兴趣的是GPL许可证什么时候变得有限制?
例如,一家公司有一个专有的软件产品,它只能与MySQL一起使用,而不是其他数据库系统。以下情况是否合法?
I don''t feel very confident when it comes to software licenses. But
there are some cases I would like to make myself clear. What I am
particulary interested in is when does GPL license become restrictive?
For example say a company has a proprietary software product that only
works with MySQL and no other database system. Are the following cases
legal?




这取决于MySQL客户端库是否为LGPL(最高版本为3)

或GPL(从版本4开始)。但是PostgreSQL论坛可能是一个讨论这个问题的完全不合适的地方。


-

Peter Eisentraut pe ***** @ gmx.net

------------- --------------(广播结束)---------------------------

提示3:如果通过Usenet发布/阅读,请发送适当的

subscribe-nomail命令到 ma ******* @ postgresql.org ,以便您的

消息可以干净地通过邮件列表



That depends on whether the MySQL client library is LGPL (up to version 3)
or GPL (from version 4 on). But a PostgreSQL forum is probably an
entirely inappropriate place to discuss this.

--
Peter Eisentraut pe*****@gmx.net
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly


这篇关于关于GPL和专有软件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆