Re: PEAR developers guide
| From: | Stig S. Bakken | Date: | Sun, 12 May 2002 13:52:52 +0000 |
| Subject: | Re: PEAR developers guide | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-6060@lists.php.net to get a copy of this message | ||
On Sun, 2002-05-12 at 10:31, Martin Jansen wrote:
> On Sat, 11 May 2002 14:07:57 -0600 (MDT), Eric wrote:
>
> >A "Getting Started" section would be nice to have in here. I just started
> >looking at PEAR yesterday, and it seems that either the information on the
> >website isn't organized well, or there is just too much confusion between
> >PEAR and PHP.
>
> This has also been requested by another person. I don't think that
> this really belongs into the developers guide, but I'll surely write
> a "Getting started" chapter.
:-)
> >1) pear requires --with-xmlrpc (seems undocumented?). The pear program
> >exits with a non-descriptive error if extension_loaded("xmlrpc") fails.
>
> Yeah, we could actually print a nicer error message. Stig?
I have something in the works. All xmlrpc operations are done through
the PEAR_Remote class, which will use the xmlrpc extension if available,
or fall back to the XML_RPC package if not. The XML_RPC package is
bundled with PHP as of two days ago.
> >2) the go-pear script downloads and installs pear packages, but does not
> >register them (most notably the PEAR package). chicken/egg problem?
>
> You should blame Tomas for this :-).
All it has to do is "pear install -r ..." to register stuff as
installed. Let me know if you get any problems with this Tomas.
> >I'm willing to help with documentation and organization. As I'm new, I
> >don't really know what to do yet. Is there a PEAR "TODO" list?
>
> http://cvs.php.net/co.php/pear/TODO
- Stig