Re: RFC: PEAR Changes / Scope
| From: | Martin Jansen | Date: | Sun, 11 Nov 2001 17:50:46 +0000 |
| Subject: | Re: RFC: PEAR Changes / Scope | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2812@lists.php.net to get a copy of this message | ||
On Sun, 11 Nov 2001 17:14:21 +0100, Michael Haertl wrote:
>Martin Jansen wrote:
>>
>> I should have said: Only the installer code and the PEAR base
>> libraries will remain as part of each PHP distribtion ;-).
>
>That leaves the question, what's the difference between PEAR base
>libraries and the "CORE" packages, Lux wanted to have? E.g. is PEAR::DB
>a base library?
To stick to your example, PEAR::DB is no base library using the
definition that was actual until the recent discussion started.
The files, that contain the base libraries, currently are
php4/pear/PEAR.php and php4/pear/PEAR/*.php, since they contain
code, that most other PEAR classes use (error reporting, destructors),
or since this files provide code, that is necessary to install
other PEAR components.
With the new definition, that has been worked out in the past
discussion, the PEAR base library will be the same than the
PEAR core. (If I interpreted everything right, that has been
said.)
>I guess, this has been discussed before. If so, this should go to the
>FAQ to prevent threads like this one from becoming such beasts :)
You are right. But as long as there is no final decision about
such things, they won't go in the FAQ.
- Martin
--
Martin Jansen, <mail@martin-jansen.de>
http://www.martin-jansen.de/