[development] Modules that integrate non-GPL PHP apps violate the GPL.

Gerhard Killesreiter gerhard at killesreiter.de
Thu Aug 30 23:16:25 UTC 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Piermaria Maraziti schrieb:
> At 23.04 30/08/2007, you wrote:
> 
> <delurking>
> 
>> For example, this API argument: by prohibiting use of APIs to bridge
>> differently-licensed applications (and aren't APIs developed
>> *precisely* to bridge two different applications?) we're forcing a
>> "dumbing down" of work (and sundry other potential problems and
>> risks) by legally requiring the bypassing of established application
>> methodologies (such as security protocols) to write direct queries to
>> databases.
> 
> If GPL programs do exist in windows (and mac) environments it is fairly
> obvious that use API of differently-licensed applications... or they
> write pixels directly in the graphic card and sectors directly in the
> hard disk?
> 
> Sorry to be rude but this had to be said this way... if I'm wrong I
> apologize, but I think I'm not.

You are completely wrong and you had better stayed in some dark corner.

The "problem" we are facing is due to the nature of how PHP and probably
other scripting languages work. The situation isn't comparable to a
compiled programms.

One could argue that one shouldn't place PHP programms under the GPL
license.

Cheers,
	Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG10/Ifg6TFvELooQRAjQwAJ9Gd/Fa1wyyzBdOCoUoU/X1R9p4EACgpj9m
yAQXsDpzuHapE0cB3hf10OA=
=f12K
-----END PGP SIGNATURE-----


More information about the development mailing list