Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35137 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38136 invoked by uid 1010); 3 Feb 2008 18:05:43 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 38121 invoked from network); 3 Feb 2008 18:05:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Feb 2008 18:05:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 85.10.196.195 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 85.10.196.195 serveforce1.backendmedia.com Linux 2.6 Received: from [85.10.196.195] ([85.10.196.195:58243] helo=serveforce1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 93/C0-31328-67206A74 for ; Sun, 03 Feb 2008 13:05:43 -0500 Received: from Soitgoes (p57BB6566.dip.t-dialin.net [87.187.101.102]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by serveforce1.backendmedia.com (Postfix) with ESMTP id 90A901224BE3; Sun, 3 Feb 2008 19:05:32 +0100 (CET) To: "Steph Fox" In-Reply-To: <002201c86689$b5f95c30$c6fc1f3e@foxbox> X-Priority: 3 References: <01c801c865d8$2e837e90$c6fc1f3e@foxbox> <14581063.20080203002104@marcus-boerger.de> <005201c8660f$66a2b160$c6fc1f3e@foxbox> <47A58686.60707@lsces.co.uk> <452173393.20080203122435@marcus-boerger.de> <002201c86689$b5f95c30$c6fc1f3e@foxbox> Message-ID: <8B40C30C-FD82-47AE-9960-B108CE16FA3F@pooteeweet.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Sun, 3 Feb 2008 19:05:07 +0100 Cc: "Marcus Boerger" , "Lester Caine" , "PHP internals" X-Mailer: Apple Mail (2.915) X-backendmedia-com-MailScanner-Information: Please contact the ISP for more information X-backendmedia-com-MailScanner: Found to be clean X-backendmedia-com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=0.093, required 6, AWL -0.01, RDNS_DYNAMIC 0.10) X-backendmedia-com-MailScanner-From: mls@pooteeweet.org X-Spam-Status: No Subject: Re: [PHP-DEV] Splitting the subject: the PECL/PHP relationship From: mls@pooteeweet.org (Lukas Kahwe Smith) On 03.02.2008, at 18:24, Steph Fox wrote: > Hi Marcus, > >> Anyway my idea is to start everything in PECL and >> to to move everything out that can be moved out. And that includes >> all MySQL >> extensions as well as SQLite. Only this way people will use the PELC >> infrastructure. Otherwise we would just reduce functionality of >> PHP. And btw >> nearly all linux distributions today offer a bunch of PECL >> extensions, and >> for windows we offer DLLs for most PECL extensions for a long time >> now. > > The problem with this, as I wrote earlier, is that people relying on > hosting can't use them, and hosts tend not to know as much as they > could about PHP or its extensions. There does need to be a basic > agreement here about what PHP is without any additions. IMHO that > should be the minimum necessary to build a simple website, ie even > if your host knows nothing about PHP it's still possible to do > something useful with it. I suggested SQLite as a way of ensuring > that there is _some_ database in PHP regardless of whether the host > has added something or not. PDO should be built-in anyway. Neither > is the case under doze @ present - both are separate entities that > have to be explicitly enabled, i.e. there is no intrinsic database > support in PHP. And yes, you do get Windows hosting these days. > > Also, we can't rely on linux distributions/the availability of DLLs > on php.net for distribution. There needs to be a single simple cross- > platform method for getting hold of extensions for PHP - but I think > Greg's so close to achieving that, it isn't really an issue. The > problem of zero QA, is. I am not sure if I misunderstood some other persons proposal, but at least my proposal was that the final thing we ship as version xyz of PHP would include a set of PECL extensions along with core that we deem as necessary for the bulk of our users solving the web problem. As such we could even publish a list of additional extensions we recommend to hosters to also install, though the question is if we can also QA them as part of the release process. regards, Lukas