Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35159
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.178 cause and error)
Reply-To: jani.taskinen@iki.fi
To: Marcus Boerger <helly@php.net>
Cc: Steph Fox <steph@zend.com>, internals <internals@lists.php.net>
In-Reply-To: <14581063.20080203002104@marcus-boerger.de>
References: <01c801c865d8$2e837e90$c6fc1f3e@foxbox>
	 <14581063.20080203002104@marcus-boerger.de>
Content-Type: text/plain
Date: Mon, 04 Feb 2008 11:18:24 +0200
Message-ID: <1202116704.4165.3.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Splitting the subject: the PECL/PHP relationship
From: jani.taskinen@sci.fi (Jani Taskinen)

I'd like everything in PECL. Even the core. And yes, it is quite doable.

--Jani


On Sun, 2008-02-03 at 00:21 +0100, Marcus Boerger wrote:
> Hello Steph,
> 
>   what I want is php-src as minimum you can depend on. And php-default as
> release managers playground. The RM can then say what he thinks is mature
> enough to make it into a release.
> 
> marcus
> 
> Saturday, February 2, 2008, 9:14:12 PM, you wrote:
> 
> > Hi all,
> 
> > Just so's Marcus and I don't have to keep cross-posting here... The problems
> > of PECL vs core extensions are many, and exist with or without the PDO/CLA 
> > debate.
> 
> > Marcus (among others) says he wants to get as many extensions as possible 
> > out of the core and into PECL. I agree fully with this as a long-term aim, 
> > but feel strongly that the PECL infrastructure is not equipped to support it
> > well at present.
> 
> > 1) Distribution woes need to end. With the work Greg's been doing lately on 
> > PHP_Archive/Phar, that's very close to being attainable now in the physical 
> > 'getting PECL'd extensions out to people' sense, but unless people are 
> > running CLI or CGI or have access to their own php.ini they still can't do 
> > much with those extensions. So we have to seriously consider how to 
> > recommend extensions to hosts, other than by shipping them with the PHP 
> > core.
> 
> > 2) Maintenance status needs to be part of the equation.
> 
> > 3) Stability needs to be part of the equation.
> 
> > 4) Appropriateness to a given PHP branch needs to be part of the equation.
> 
> > 5) CS and documentation need to be part of the equation.
> 
> > Thoughts?
> 
> > - Steph 
> 
> 
> 
> 
> Best regards,
>  Marcus
> 
-- 
Patches/Donations: http://pecl.php.net/~jani/