Re: PHP licensing issues

Hello, Can you provide more details about which Zend files are using GPL/LGPL code? I can't find them, the only files mentioning the GPL are those generated (.c and .h files) by Bison from .y files (like zend_ini_parser.y and zend_language_parser.y). If GPL/LGPL (or other) code is found inside extensions, then they shouldn't be bundled with PHP itself. Non-GPL'ed products embedding PHP should take care of this by not bundling them too. Regards, Patrick Allaert 2009/5/19 <Ossi.Niiranen@tieto.com>: > Dear all, > > I had some difficulties deciding which of the email lists should I post > my query to, but in the end figured that this might be a quality issue > so perhaps this is the right list. > > We are reviewing the licensing of the standard PHP distribution to > identify all relevant licenses and their corresponding license > obligations that we need to comply with if we distribute PHP. I figured > it would be a relatively simple task with the PHP website stating that > the main license is the PHP license and other licenses are compatible > with it. Having now run a source code checker on the distribution, I was > surprised to find out several instances of GPL and LGPL licensed code, > and am now concerned that due to the GPL/LGPL copyleft effect we should > in fact be distributing the whole under the GPL. > > A few GPL/LGPL licensed components/files include: > - Various Zend files included with the distribution > - Files in ext/mbstring/libmbfl/mbfl/ (many if not all of them seem to > form part of the "streamable kanji code filter and converter") > > I assume these issues have already been looked at and there's a simple > explanation for the perceived license conflict, but I did not find any > reference to them in the mailing list archives. Would someone mind > clarifying it? > > -- > Ossi Niiranen, Legal Counsel