Re: why don't most classes extend PEAR?
| From: | greg keraunen | Date: | Sat, 08 Sep 2001 08:24:35 +0000 |
| Subject: | Re: why don't most classes extend PEAR? | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1843@lists.php.net to get a copy of this message | ||
Stig Sæther Bakken wrote:
>
> [greg keraunen <gk@proliberty.com>]
> > Martin Jansen wrote:
> > > Ahh, obviously you are using the wrong PEAR.php :-). Have a look at
> > > PEAR.php in php4/pear (not in php4/pear/PEAR/).
> >
> > I wasn't looking in php4 at all. I read some messages that seemed to
> > imply that the new home for pear was in pear directory.
> >
> > Are you saying that php4/pear is the official home of pear? If so, what
> > is the purpose of pear directory?
>
> php4/pear/ was the official home for pear, now it is pear/. All new
> packages should go into pear/, and most of the code in php4/pear/ will
> be moved there eventually (when people can install stuff from pear/
> without using CVS).
So it appears that the php4/pear/PEAR.php file that Martin says I should
be using has not been moved to pear/ yet.
Is it going to move eventually? Or are you going to a system where
PEAR.so will be required as it is now in the pear/PEAR/PEAR.php file?
- greg