Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:6318 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62525 invoked by uid 1010); 9 Dec 2003 20:42:48 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 62468 invoked from network); 9 Dec 2003 20:42:48 -0000 Received: from unknown (HELO asuka.nerv) (24.112.18.98) by pb1.pair.com with SMTP; 9 Dec 2003 20:42:48 -0000 Received: (qmail 28777 invoked from network); 9 Dec 2003 15:38:01 -0000 Received: from rei.nerv (HELO dummy.com) (rei@192.168.1.1) by asuka.nerv with SMTP; 9 Dec 2003 15:38:01 -0000 Reply-To: ilia@prohost.org To: "Wez Furlong" , "Jani Taskinen" , PHP Internals Date: Tue, 9 Dec 2003 15:53:39 -0500 User-Agent: KMail/1.5.4 References: <061601c3be92$67152ed0$8802a8c0@obsidian> In-Reply-To: <061601c3be92$67152ed0$8802a8c0@obsidian> Organization: Prohost.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200312091553.40931.ilia@prohost.org> Subject: Re: [PHP-DEV] oci in pecl... From: ilia@prohost.org (Ilia Alshanetsky) On December 9, 2003 03:24 pm, Wez Furlong wrote: > The flip side is that we can provide them with a "localized" > (not in the i18n sense!) fix much sooner. The current snapshot system contains a patched version (after the fix is applied) within 2 hours at most for source distributions and 4 hours for win32 distributions. > This isn't really a problem as you tend to mark all bug > reports as bogus anyway, and no one else provides support. I beg to differ, there are plenty of people (not to say that there couldn't be more ;) ) who handle bugs etc... you need to look no further then the NEWS file. I may have misunderstood you, so please correct me if I am wrong, but it seems are you advocating a system where by modules are compiled as shared. This approach would open a whole can of worms with users using conflicting module versions, trying to load same modules more then once and so on. Not only will this be a headache for the users, but also for the QA/developers who wish to solve user reported problems. Without a way to determine the exact version of the module it'd be nearly impossible to determine what code is the user actually using. Ilia