[development] Modules that integrate non-GPL PHP apps violate theGPL.
gerhard at killesreiter.de
Thu Aug 30 19:11:26 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Boris Mann schrieb:
> On 8/30/07, FGM <fgm at osinet.fr> wrote:
>> I don't agree with the
>> FSF's interpretation that invoking independent PHP scripts
>> constitutes linking, but that appears to be their stance.
Well, it makes a lot of sense.
> Also agreed. What about a C library on the commandline? What about
> command line invocation, through PHP, of anything?
See Jeff's mail.
>> its purpose is to make a single
>> unit of software out of those parts.
> Don't agree. The purpose is to loosely couple two separate pieces of
> code (for licensing, code maintenance, or 1000s of other reasons). Do
> you want me to put a web services interface in between just to jump
> through hoops?
[x] SEND PIX!!!^1
> (reading further down....)
> If you do want to distribute, and the "other code" isn't GPL, then
> you'll need to use web services. Shared address space my ass....that
> just happens to be how scripting languages like PHP all work.
GPLed by design. Another compelling feature. :)
> So, um, what if, completely separately, I am running app1 which is GPL
> and app2 which is non GPL and they are running on the same PHP
How'd you want to do that?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the development