Re: why don't most classes extend PEAR?
| From: | Martin Jansen | Date: | Sat, 08 Sep 2001 08:55:51 +0000 |
| Subject: | Re: why don't most classes extend PEAR? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1846@lists.php.net to get a copy of this message | ||
On Sat, 08 Sep 2001 01:48:27 -0700, greg keraunen wrote:
>Martin Jansen wrote:
>> >Is it going to move eventually?
>>
>> PEAR.php will stay in php4/pear because it should be delivered with
>> each new PHP release (as I said a few days before: PEAR.php as some
>> kind of VIP status, because it is used by a lot of [perhaps also by
>> most] PEAR components).
>
>I guess I should have asked, is it going to be replicated in pear/?
No, there is no need for replicating it.
>I'm not trying to go round and round the pear tree here :-)
>It just seems awkward to have one special VIP file that people have to
>get from php4/pear and all the rest come from pear/.
Once again :-): The files from php4/pear are bundled into each new
release of PHP. So they are _automatically_ on your system: You
do not need to get PEAR.php from CVS - it's already there!
The packages from pear/ will be installed by this installer
thingie (via command line or via a web interface - whatever
you like more) and they will use PEAR.php that is already
on your system.
- Martin