Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39575
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 88.198.8.16 as permitted sender)
To: Marcus Boerger <helly@php.net>
In-Reply-To: <464710978.20080801220313@marcus-boerger.de>
References: <464710978.20080801220313@marcus-boerger.de>
Message-ID: <A079A766-23CF-4288-A36F-17FF90E9C428@php.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Sun, 3 Aug 2008 21:38:29 +0200
Cc: PHP Internals List <internals@lists.php.net>,
 =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>
Subject: Re: [PHP-DEV] Another PECL candidate and more extension considerations.
From: lsmith@php.net (Lukas Kahwe Smith)


On 01.08.2008, at 22:03, Marcus Boerger wrote:

> 1) Move everything that can be disabled to PECL. This renders the  
> resulting
> PHP pretty much useless for allmost everyone and thus forces people to
> start using PECL and distributors even more to carefully select. In  
> the
> long run this is the way to go anyway and was discussed as such many  
> times
> already. Also any ext that moves to PECL should be enabled by  
> default in
> PECL of course. A reason to do that move right now would be the  
> approaching
> of SVN and the opportunity to go with a clean code layout.

Just to make it clear for me, you are talking about the mid-to-long  
term.

> 2) We might not really be ready for one and continue doing as we've  
> always
> done. Select a nice collection of extension that aims to make the  
> majority
> of our userbase happy. And suggest defaults this way whether or not  
> they
> are enabled by default. The default enabled exts are just a stronger
> suggesttion that we think people should be able to rely on.


Well this is indeed an entirely different model if we would go with  
1). I presume we could offer a "recommended" list maybe. I also assume  
that this would shift things towards the linux distros similar to how  
things are with the linux kernel. Anyways the first thing is to have  
the distribution of PECL packages rock solid. So imho lets wait and  
see how pyrus pans out. That being said, PHP 6 would be the best point  
in time if we ever want to do this for the next half decade.

regards,
Lukas Kahwe Smith
smith@pooteeweet.org