Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10062 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56456 invoked by uid 1010); 24 May 2004 10:39:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 56430 invoked from network); 24 May 2004 10:39:52 -0000 Received: from unknown (HELO mx.thebrainroom.net) (65.200.24.98) by pb1.pair.com with SMTP; 24 May 2004 10:39:52 -0000 Received: by mx.thebrainroom.net (Postfix, from userid 517) id E99A514880C0; Mon, 24 May 2004 03:39:49 -0700 (PDT) Received: from tron (obsidian.thebrainroom.net [82.133.1.142]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx.thebrainroom.net (Postfix) with ESMTP id DED45148809B; Mon, 24 May 2004 03:39:46 -0700 (PDT) To: "'Rainer Schaaf'" , Date: Mon, 24 May 2004 11:39:47 +0100 Organization: The Brain Room Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 In-Reply-To: <182521968109.20040524122755@pdflib.com> Thread-Index: AcRBeaBV1Q7y/tj4TfSGThnTRAuOBQAAJb2A Message-ID: X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on jc.thebrainroom.net X-Spam-Status: No, hits=2.0 required=5.0 tests=NEW_DOMAIN_EXTENSIONS autolearn=no version=2.63 X-Spam-Level: * X-TBR-Filter: Virus scanned and defanged Subject: RE: [PHP-DEV] New PDFlib extension for PHP5 From: wez@thebrainroom.com ("Wez Furlong") References: <182521968109.20040524122755@pdflib.com> Hello Rainer, A few of us have been planning to move the pdflib extension into PECL (http://pecl.php.net) for a little while now; it sounds like an excellent time to make this move, because it will allow you to make supplemental releases outside of the PHP 5 core release cycle. Here is a possible release plan: 1/ Move the current code into PECL 2/ Make a release (so that people may choose to use the code they are used to) 3/ Merge your new code and bump the extension version to the next major (eg: from 1.x to 2.0) 4/ Make a release 5/ Update and make additional releases whenever you like How does that sound to you? > - disables VIRTUAL_DIR support (use SerachPath instead) > - disables CHECK_OPEN_BASEDIR checks This doesn't sound too hot for shared hosters. --Wez.