Hey!
I am not very good with English - its my second language, German my first - so I wanted to ask about something that has to do with redistribution.
Currently, in my project I am configuring PHP and then compiling it, plus a few extensions (v8js, yar, uv, pthreads, PHP-CPP) to a set of static libraries (libphp5.a, libtsrm.a, libzend.a, libphp-v8js.a, …). In the end process, this is all combined, together with other libraries, into a dynamic library.
This project is not public yet, since I dont know if:
- I can actually link PHP into my dynamic library without tripping on any licensing?
- That applies to all extensions using the PHP license?
- I have to redistribute anything else but the headers? (of course, a copyright notice to php plus original headers of the main library and extension swould be distributed all together, excluded would be the actual binaries/utilities, phar, php, php-cgi, etc.)
Would be great to know if I can work it that way or not! :) Because the least I want is to run against a wall… o.o
Kind regards, Ingwie.
Hey!
I am not very good with English - its my second language, German my
first - so I wanted to ask about something that has to do with
redistribution.Currently, in my project I am configuring PHP and then compiling it,
plus a few extensions (v8js, yar, uv, pthreads, PHP-CPP) to a set of
static libraries (libphp5.a, libtsrm.a, libzend.a, libphp-v8js.a, …).
In the end process, this is all combined, together with other
libraries, into a dynamic library.This project is not public yet, since I dont know if:
- I can actually link PHP into my dynamic library without tripping on
any licensing?- That applies to all extensions using the PHP license?
- I have to redistribute anything else but the headers? (of course, a
copyright notice to php plus original headers of the main library and
extension swould be distributed all together, excluded would be the
actual binaries/utilities, phar, php, php-cgi, etc.)Would be great to know if I can work it that way or not! :) Because
the least I want is to run against a wall… o.o
-
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. -
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
and
- Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes PHP software, freely available from
http://www.php.net/software/".
sound relatively clear. I'm not really getting whether you distribute
source or binaries. In general providing that licenses in some "about"
dialog or referring to it from your README or whatever should be fine.
If you can describe in more detail I assume that group@qhp.net (I'm no
member there can't speak for them) will help you ..,. but mind if you
really go into legal issues: Ask two lawyers and you receive three
answers. ;-)
johannes
On Fri, Apr 25, 2014 at 7:08 PM, Johannes Schlüter
johannes@schlueters.dewrote:
Hey!
I am not very good with English - its my second language, German my
first - so I wanted to ask about something that has to do with
redistribution.Currently, in my project I am configuring PHP and then compiling it,
plus a few extensions (v8js, yar, uv, pthreads, PHP-CPP) to a set of
static libraries (libphp5.a, libtsrm.a, libzend.a, libphp-v8js.a, …).
In the end process, this is all combined, together with other
libraries, into a dynamic library.This project is not public yet, since I dont know if:
- I can actually link PHP into my dynamic library without tripping on
any licensing?- That applies to all extensions using the PHP license?
- I have to redistribute anything else but the headers? (of course, a
copyright notice to php plus original headers of the main library and
extension swould be distributed all together, excluded would be the
actual binaries/utilities, phar, php, php-cgi, etc.)Would be great to know if I can work it that way or not! :) Because
the least I want is to run against a wall… o.o
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.and
- Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes PHP software, freely available from
http://www.php.net/software/".sound relatively clear. I'm not really getting whether you distribute
source or binaries. In general providing that licenses in some "about"
dialog or referring to it from your README or whatever should be fine.
If you can describe in more detail I assume that group@qhp.net (I'm no
member there can't speak for them) will help you ..,. but mind if you
really go into legal issues: Ask two lawyers and you receive three
answers. ;-)johannes
--
Where does the group alias go to, anyway?
--Kris
Where does the group alias go to, anyway?
PHP Group
Thies C. Arntzen, Stig Bakken, Shane Caraveo, Andi Gutmans, Rasmus
Lerdorf, Sam Ruby, Sascha Schumann, Zeev Suraski, Jim Winstead, Andrei
Zmievski
http://php.net/credits.php
johannes