Re: Licensing...
| From: | Martin Jansen | Date: | Thu, 19 Jul 2001 06:13:46 +0000 |
| Subject: | Re: Licensing... | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-209@lists.php.net to get a copy of this message | ||
On Wed, 18 Jul 2001 22:44:24 -0500, Keith Schoenefeld wrote:
>What license is the
>Pear code released under?
Most of the PEAR classes are released under the PHP License. Have a
look at the header of e.g. DB.php:
//
+----------------------------------------------------------------------+
// | PHP version 4.0
|
//
+----------------------------------------------------------------------+
// | Copyright (c) 1997-2001 The PHP Group
|
//
+----------------------------------------------------------------------+
// | This source file is subject to version 2.02 of the PHP license,
|
// | that is bundled with this package in the file LICENSE, and is
|
// | available at through the world-wide-web at
|
// | http://www.php.net/license/2_02.txt.
|
// | If you did not receive a copy of the PHP license and are unable to
|
// | obtain it through the world-wide-web, please send a note to
|
// | license@php.net so we can mail you a copy immediately.
|
//
+----------------------------------------------------------------------+
When you are using PEAR DB you are using the same license as if you
are using substr(), nl2br(), fopen() or any other function that comes
with PHP.
>Can I build a GPL program that calls the DB
>class?
Yes, of course.
>I would love to use the pear DB class (and it's other functions), but I
>only want to do so within the licensing of the GPL. Is anyone out there
>able to help me?
Did you ever think, that using mysql_connect() in a GPL project is
a problem? It isn't a problem indeed. The same applies for PEAR DB:
It stands under the same license, than mysql_connect() does, so there
is no problem in using it in a GPL licensed project.
- Martin