I was wondering what the licensing issues for app frameworks (or any
included PHP classes/libs) are. I'm creating a rather large PHP
application for a company, and they'd like to potentially resell it to
some of their customers.
Can I safely use GPL'd libraries, classes, etc. (i.e. PearDB) and
John Wells said:
Can I safely use GPL'd libraries, classes, etc. (i.e. PearDB) and
resources that fall under other open source licenses when developing the
app and let them redistribute accordingly, or would that be a violation?
I don't know anything about the licensing terms of PearDB.
Read
At 17:17 22-1-03, you wrote:
I was wondering what the licensing issues for app frameworks (or any
included PHP classes/libs) are. I'm creating a rather large PHP
application for a company, and they'd like to potentially resell it to
some of their customers.
Can I safely use GPL'd libraries,
Chris Hayes said:
The GPL can be a headache to figure out when it gets to complicated
situations.
My uneducated working conclusion is that the GPL prevents you from
selling GPL-ed code as is, or improved GPL-ed code. Selling GPL-ed
code, even if you improved it, is dead wrong. Even if you
However - if you want to sell software under a closed licence you will
need to be carefull to avoid 'linking' with gpl'd code.
The problem is that 'linking' as used in the gpl seems to refer to C
programming - and is an unclear term when refering to php.
Yeah...that's really what I'm
Chris Hayes wrote:
At 17:17 22-1-03, you wrote:
I was wondering what the licensing issues for app frameworks (or any
included PHP classes/libs) are. I'm creating a rather large PHP
application for a company, and they'd like to potentially resell it to
some of their customers.
Can I safely use
John Wells said:
However - if you want to sell software under a closed licence you will
need to be carefull to avoid 'linking' with gpl'd code.
The problem is that 'linking' as used in the gpl seems to refer to C
programming - and is an unclear term when refering to php.
I know I read this
Peter Hutnick said:
Yeah...that's really what I'm wondering. If I have my own code, but
make function calls and the like to script libraries licensed under
the GPL, does it mean my code will have to be GPL'd as well?
In a word, yes.
Even if the script libraries are themselves just PHP
John,
I am not an expert of copyright law and licenses, but this
URL might help you answer some of your questions:
http://www.gnu.org/licenses/gpl-faq.html
Specifically, look at the questions under the heading,
Combining work with code released under the GPL, as they
seem to be exactly what you
Chris,
Sheesh. I'd read it about 5 times but revisited just now. Somehow I
missed the key phrase which are themselves interpreted..
Here's the full relevant excerpt:
Another similar and very common case is to provide libraries with the
interpreter which are themselves interpreted. For
John Wells said:
Peter Hutnick said:
Yeah...that's really what I'm wondering. If I have my own code, but
make function calls and the like to script libraries licensed under
the GPL, does it mean my code will have to be GPL'd as well?
In a word, yes.
Even if the script libraries are
11 matches
Mail list logo
