GPL和PHP应用程序的问题 [英] GPL and issues with PHP applications
问题描述
我可以看到很多针对GPL的噪音。 INAL，但许多文章建议我们不能用商业软件添加GPLed软件;如果我们添加，
商业软件将自动成为GPL。
所以，我想知道，如果许可证问题影响了你的
business / PHP编码工作。例如，您不能简单地将PHPMailer
class< http://phpmailer.sourceforge.net/> ;,与任何商业
应用程序一起添加。那么，在那种情况下你会做什么？或任何此类个人
经历？ TIA。
-
|只是另一个PHP圣人|
电子邮件：rrjanbiah-at-Y！com
I could see lot of noise against GPL. INAL, but many articles suggest
that we cannot add GPLed software with commercial software; if we add,
the commercial software will automatically become GPLed.
So, I would like to know, if the license issue affected your
business/PHP coding work. For example, you can''t simply add PHPMailer
class <http://phpmailer.sourceforge.net/>, with any of your commercial
applications. So, what would you do in that case? or Any such personal
experiences? TIA.
--
| Just another PHP saint |
Email: rrjanbiah-at-Y!com
推荐答案
你好，
在07/15/2004 05:20 AM，R。Rajesh Jeba Anbiah写道：
Hello,
On 07/15/2004 05:20 AM, R. Rajesh Jeba Anbiah wrote:
我可以看到很多针对GPL的噪音。 INAL，但很多文章都建议我们不能用商业软件添加GPLed软件;如果我们添加，
商业软件将自动成为GPL。
所以，我想知道，如果许可证问题影响了您的业务/ PHP编码工作。例如，您不能简单地将PHPMailer
类< http://phpmailer.sourceforge.net/> ;,与任何商业
应用程序一起添加。那么，在那种情况下你会做什么？或任何这样的个人经历？ TIA。
I could see lot of noise against GPL. INAL, but many articles suggest
that we cannot add GPLed software with commercial software; if we add,
the commercial software will automatically become GPLed.
So, I would like to know, if the license issue affected your
business/PHP coding work. For example, you can''t simply add PHPMailer
class <http://phpmailer.sourceforge.net/>, with any of your commercial
applications. So, what would you do in that case? or Any such personal
experiences? TIA.
这是正确的。如果您使用仅作为GPL许可的软件包，则只需将其与其他GPL软件链接（如果您愿意，请将其称为）。您可能仍然以GPL的价格出售您的软件，但我想您不想打开商业应用程序的来源。
- -
问候，
Manuel Lemos
PHP类 - 免费准备使用用PHP编写的OOP组件
http://www.phpclasses.org/
PHP评论 - PHP书籍和其他产品的评论
http ：//www.phpclasses.org/reviews/
Metastorage - 数据对象关系映射层生成器
http://www.meta-language.net/metastorage.html
That''s correct. If you use a package that is license only as GPL you
only link it (call it if you prefer) with other GPL software. You may
still sell your software as GPL but I suppose that you do not want to
open the source of your commercial application.
--
Regards,
Manuel Lemos
PHP Classes - Free ready to use OOP components written in PHP
http://www.phpclasses.org/
PHP Reviews - Reviews of PHP books and other products
http://www.phpclasses.org/reviews/
Metastorage - Data object relational mapping layer generator
http://www.meta-language.net/metastorage.html
Manuel Lemos< ml **** @ acm.org>在留言新闻中写道：< 2l ************ @ uni-berlin.de> ...
Manuel Lemos <ml****@acm.org> wrote in message news:<2l************@uni-berlin.de>...
你好，
07 / 15/2004 05:20 AM，R。Rajesh Jeba Anbiah写道：
Hello,
On 07/15/2004 05:20 AM, R. Rajesh Jeba Anbiah wrote:
我可以看到很多针对GPL的噪音。 INAL，但很多文章都建议我们不能用商业软件添加GPLed软件;如果我们添加，
商业软件将自动成为GPL。
所以，我想知道，如果许可证问题影响了您的业务/ PHP编码工作。例如，您不能简单地将PHPMailer
类< http://phpmailer.sourceforge.net/> ;,与任何商业
应用程序一起添加。那么，在那种情况下你会做什么？或任何这样的个人经历？ TIA。
I could see lot of noise against GPL. INAL, but many articles suggest
that we cannot add GPLed software with commercial software; if we add,
the commercial software will automatically become GPLed.
So, I would like to know, if the license issue affected your
business/PHP coding work. For example, you can''t simply add PHPMailer
class <http://phpmailer.sourceforge.net/>, with any of your commercial
applications. So, what would you do in that case? or Any such personal
experiences? TIA.
那是对的。如果您使用仅作为GPL许可的软件包，您只需将其与其他GPL软件链接（如果您愿意，请将其调用）。您可能仍然以GPL的形式出售您的软件，但我认为您不想打开商业应用程序的来源。
That''s correct. If you use a package that is license only as GPL you
only link it (call it if you prefer) with other GPL software. You may
still sell your software as GPL but I suppose that you do not want to
open the source of your commercial application.
谢谢的确，对你的评论。我真的很想知道其他PHP
saints在这些情况下会做什么。
-
|只是另一个PHP圣人|
电子邮件：rrjanbiah-at-Y！com
Thanks indeed, for your comments. I really wonder what other PHP
saints would do in those situations.
--
| Just another PHP saint |
Email: rrjanbiah-at-Y!com
查看PHP的套接字函数并创建一些POP / IMAP / SMTP
与他们对象...这就是我要做的......
R. Rajesh Jeba Anbiah写道：
Look into the socket functions of PHP and create some POP/IMAP/SMTP
object with them... thats what I''d do...
R. Rajesh Jeba Anbiah wrote:
Manuel Lemos< ml **** @ acm.org>在消息新闻中写道：< 2l ************ @ uni-berlin.de> ...
Manuel Lemos <ml****@acm.org> wrote in message news:<2l************@uni-berlin.de>...
你好，
在07/15/2004 05:20 AM，R。Rajesh Jeba Anbiah写道：
Hello,
On 07/15/2004 05:20 AM, R. Rajesh Jeba Anbiah wrote:
我可以看到很多针对GPL的噪音。 INAL，但很多文章都建议我们不能用商业软件添加GPLed软件;如果我们添加，
商业软件将自动成为GPL。
所以，我想知道，如果许可证问题影响了您的业务/ PHP编码工作。例如，您不能简单地将PHPMailer
类< http://phpmailer.sourceforge.net/> ;,与任何商业
应用程序一起添加。那么，在那种情况下你会做什么？或任何这样的个人经历？ TIA。
I could see lot of noise against GPL. INAL, but many articles suggest
that we cannot add GPLed software with commercial software; if we add,
the commercial software will automatically become GPLed.
So, I would like to know, if the license issue affected your
business/PHP coding work. For example, you can''t simply add PHPMailer
class <http://phpmailer.sourceforge.net/>, with any of your commercial
applications. So, what would you do in that case? or Any such personal
experiences? TIA.
这是对的。如果您使用仅作为GPL许可的软件包，您只需将其与其他GPL软件链接（如果您愿意，请将其调用）。您可能仍然以GPL的形式出售您的软件，但我认为您不想打开商业应用程序的来源。
That''s correct. If you use a package that is license only as GPL you
only link it (call it if you prefer) with other GPL software. You may
still sell your software as GPL but I suppose that you do not want to
open the source of your commercial application.
谢谢的确，对你的评论。我真的很想知道其他PHP圣徒会在这些情况下做些什么。
Thanks indeed, for your comments. I really wonder what other PHP
saints would do in those situations.
这篇关于GPL和PHP应用程序的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
