[Ubuntu-BR] [Bulk] Sobre SL e como ganhar dinheiro com ele (Era: Ubuntu 8.10 Mandriva one 2009??)

[Iuri Diniz]

2008/12/15 romano <bruno em tanervoso.com.br>

> Muito obrigado pelas correções.
>
> Então se eu linkar dinamicamente todas minhas lib's usando o dlopen(),
> eu consigo usar bibliotecas GPL e não só LGPL.
>
>
Código Não GPL Compatível, só pode linkar com bibliotecas LGPL e de forma
dinâmica, seja elas via dlopen ou ld. Linkagem estática não é aceito.

A única forma de usar código GPL/LGPL em um programa fechado é fazendo fork
or exec, ou executando apenas função "main" dele (que seria o equivalente ao
fork/exec).

em http://www.gnu.org/licenses/gpl-faq.html#NFUseGPLPlugins temos:
*Can I release a non-free program that's designed to load a GPL-covered
plug-in?*

It depends on how the program invokes its plug-ins. For instance, if the
program uses *only* simple fork and exec to invoke and communicate with
plug-ins, then the plug-ins are separate programs, so the license of the
plug-in makes no requirements about the main program.

If the program dynamically links plug-ins, and they make function calls to
each other and share data structures, we believe they form a single program,
which must be treated as an extension of both the main program and the
plug-ins. In order to use the GPL-covered plug-ins, the main program must be
released under the GPL or a GPL-compatible free software license, and that
the terms of the GPL must be followed when the main program is distributed
for use with these plug-ins.

If the program dynamically links plug-ins, but the communication between
them is limited to invoking the 'main' function of the plug-in with some
options and waiting for it to return, that is a borderline case.

Using shared memory to communicate with complex data structures is pretty
much equivalent to dynamic linking.

See also the question I am writing free software that uses a non-free
library. <http://www.gnu.org/licenses/gpl-faq.html#FSWithNFLibs>


-- 
Iuri Diniz
http://iuridiniz.com [Sou um agitador, não um advogado]
http://blog.igdium.com [Linux on Limbo]