Re: updated channels rfc
| From: | Jon Parise | Date: | Wed, 03 Mar 2004 07:41:49 +0000 |
| Subject: | Re: updated channels rfc | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-160@lists.php.net to get a copy of this message | ||
On Wed, Mar 03, 2004 at 08:19:14AM +0100, Martin Jansen wrote:
> On Tue Mar 02, 2004 at 10:1707PM -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)
>
> I really do not like that particular part of your plan. Distributing the
> code that runs pear.php.net will make the life of the people that are
> maintaining the website much harder, because in addition to taking care
> that the code runs on pear.php.net, they then also will need to take
> care that it basically runs everywhere else as well.
>
> Thus I instead suggest to come up with a small package that provides the
> basic functionality like XML_RPC and some /get/ service. This package
> can then be installed and extended by interested parties that would like
> to provide a channel server for PEAR.
Right, this is exactly what I would like. I can build my own package
management backend behind the interface provided by this package
(maybe PEAR_ChannelService?).
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)