Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2266 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96763 invoked from network); 10 Jun 2003 10:02:13 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 10 Jun 2003 10:02:13 -0000 Received: from jdi.jdimedia.nl (jdi.jdimedia.nl [212.204.192.51]) by jdi.jdimedia.nl (8.12.4/8.12.4) with ESMTP id h5AA28h5025187; Tue, 10 Jun 2003 12:02:08 +0200 Date: Tue, 10 Jun 2003 12:02:08 +0200 (CEST) X-X-Sender: derick@jdi.jdimedia.nl To: Pierre-Alain Joye cc: James Cox , internals@lists.php.net, jorton@redhat.com In-Reply-To: <20030610115446.5485fb99.paj@pearfr.org> Message-ID: References: <003601c32e91$b9d3d8b0$0200a8c0@23i.net> <20030610115446.5485fb99.paj@pearfr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Why Move to PECL? From: derick@php.net (Derick Rethans) On Tue, 10 Jun 2003, Pierre-Alain Joye wrote: > On Mon, 9 Jun 2003 15:16:30 +0100 > "James Cox" wrote: > > > How do we get here? > > > > By moving PECL into the limelight. This week, I will be splitting PECL > > into it's own cvs module, and (after discussion) I'd like to create a > > version of pearweb for pecl.php.net, essentially seperating the PEAR > > and PECL projects. > > I do not agree here with pecl.php.net. From the early days of PEAR, it > contains PEAR and PECL, the roadmaps of PEAR was always to take care of > PECL inside the PEAR infrastructure. I agree, I go with Markus' aliasing and highlighting thingy. > As a sidenote, the installer currently does not support multiple master > servers. Fix it! ;) regards, Derick -- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ International PHP Magazine http://php-mag.net/ -------------------------------------------------------------------------