kdelibs and the GPL

Rob Kaper cap at capsi.com
Thu Jun 20 14:35:03 BST 2002

On Thu, Jun 20, 2002 at 03:25:54PM +0200, Rolf Magnus wrote:
> By contrast, pipes, sockets and command-line arguments are communication 
> mechanisms normally used between two separate programs. So when they are used 
> for communication, the modules normally are separate programs. But if the 
> semantics of the communication are intimate enough, exchanging complex 
> internal data structures, that too could be a basis to consider the two parts 
> as combined into a larger program. 
> ===============================================================================
> What you describe sounds like it falls into the category "intimate enough".

Well.. "ultimately judges will decide", "we *believe*" (emphasis added) and
"*could* be a *basis* to consider" (emphasis added) do not sound very

Well, um, it could be, might not be, but it could be, a basis - not an actual
reason just a basis - to consider..

A shell script can manipulate many internal and complex datastructures of
the shell itself when it is interpreted. Intimate enough to force all shell
(or for that matter, PHP/Perl, which allows you to change the PHP engine
behaviour as well) scripts to be licensed compatible to the licenses of
those environments?

The GPL is on very thin ice here and the FSF seems to know it, looking at
how they can only guess about the legal answer to the question "1 or 2".

Rob Kaper     | Gimme some love, gimme some skin,
cap at capsi.com | if we ain't got that then we ain't got much
www.capsi.com | and we ain't got nothing, nothing! -- "Nothing" by A

More information about the kde-core-devel mailing list