Re: updated channels rfc
| From: | Jon Parise | Date: | Wed, 03 Mar 2004 04:05:37 +0000 |
| Subject: | Re: updated channels rfc | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-157@lists.php.net to get a copy of this message | ||
On Tue, Mar 02, 2004 at 10:17:07PM -0500, Greg Beaver wrote:
> The next step in supporting channels will be making pearweb into a
> distributable package. I've started this work, beginning with a
> package.xml. The next step is going to be separating out the
> PEAR-specific content into an easily customizable design.
>
> It currently has about 25 dependencies, and so the -a switch is your
> friend :) (pear install -a pearweb)
>
> What I would do to begin is familiarize yourself with the basic
> structure of pearweb as it currently stands. This will help immensely,
> as you will see PEAR-only assumptions that won't work for horde, and
> this will help to separate the content out that needs to be separated.
I'm not sure I want to go down that road right now. I'm already
fairly familiar with the pearweb code, and I've been meaning to try to
run it against a PostgreSQL database, but I can't allot the time to do
any more than that right now.
However, if setting up a package distribution site means getting
pearweb running, I think we need to re-evaluate this requirement. I'd
really rather not have to set up (and maintain) a development "portal"
and backing database just to serve package archives.
> You will need to support a /get/ URI, and the XML-RPC that is available
> in pearweb/include/pear-database.php.
Ideally, this would be *all* I'd need to support (and a stripped down
XML-RPC interface, at that).
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)