Re: Another PECL candidate and more extension considerations.

From: Date: Sun, 03 Aug 2008 19:38:29 +0000
Subject: Re: Another PECL candidate and more extension considerations.
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-39575@lists.php.net to get a copy of this message
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

« previous php.internals (#39575) next »