(odpocinkove) GPL kod v komercni aplikaci
Karel Zak
zakkr na zf.jcu.cz
Úterý Červenec 1 14:46:42 CEST 2003
On Tue, Jul 01, 2003 at 02:01:26PM +0200, Martin `MJ' Mares wrote:
> > Co treba Linux kernel a nektere close source ovladace?
>
> Ty se pohybuji na prevelice tenkem lede, nebot Linus sam sice prohlasil,
> ze mu binary-only moduly nevadi a ze je za odvozene dilo nepovazuje, ale
> neni jedinym drzitelem copyrightu k jadru (jelikoz Linus narozdil od FSF
> nevyzaduje zadne copyright assignmenty, je dnes spoluautory jadra
> nekolik set osob) a nekteri z ostatnich vyvojaru (napriklad Alan Cox,
> jehoz kodu je dnes v jadru asi podstatne vice nez Linusova) s tim
> zasadne nesouhlasi.
Je zde nejaka vseobecne znama a uznavana open source licence, ktera
by umoznovala rozsirovani pomoci binary-only modulu a zaroven
chranila prava autora?
Ted koukam do FAQ a mozna pokud by bylo stanoveno nejake presne
definovane API tak by to GLP prezila :-)
If a program released under the GPL uses plug-ins, what are
the requirements for the licenses of a plug-in?
It depends on how the program invokes its plug-ins. If the
program uses fork and exec to invoke plug-ins, then the
plug-ins are separate programs, so the license for the main
program makes no requirements for them.
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, so plug-ins must be
treated as extensions to the main program. This means they
must be released under the GPL or a GPL-compatible free
software license, and that the terms of the GPL must be
followed when those plug-ins are distributed.
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.
Karel
--
Karel Zak <zakkr na zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/
Další informace o konferenci Linux