# License question

- Thread: https://externals.io/message/73803
- Original archive: https://news-web.php.net/php.internals/73803
- Started by Kevin Ingwersen on 2014-04-25T23:22:22+00:00
- Messages: 4
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #73803 — Kevin Ingwersen — 2014-04-25T23:22:22+00:00

URL: https://externals.io/message/73803#73803

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.

---

## #73804 — johannes@schlueters.de — 2014-04-26T02:08:11+00:00

URL: https://externals.io/message/73803#73804 · In reply to: #73803

> 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
> 


  1. Redistributions of source code must retain the above copyright
     notice, this list of conditions and the following disclaimer.

  2. 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

  6. 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

---

## #73806 — Kris Craig — 2014-04-26T06:26:35+00:00

URL: https://externals.io/message/73803#73806 · In reply to: #73804

On Fri, Apr 25, 2014 at 7:08 PM, Johannes Schlüter
<johannes@schlueters.de>wrote:

> 
> > […]
>
>
>   1. Redistributions of source code must retain the above copyright
>      notice, this list of conditions and the following disclaimer.
>
>   2. 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
>
>   6. 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

---

## #73813 — johannes@schlueters.de — 2014-04-26T11:00:38+00:00

URL: https://externals.io/message/73803#73813 · In reply to: #73806

> 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