Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21065 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32559 invoked by uid 1010); 6 Dec 2005 18:53:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 32544 invoked from network); 6 Dec 2005 18:53:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Dec 2005 18:53:44 -0000 X-Host-Fingerprint: 204.11.219.139 lerdorf.com Linux 2.4/2.6 Received: from ([204.11.219.139:54001] helo=colo.lerdorf.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id F5/9C-14828-73ED5934 for ; Tue, 06 Dec 2005 13:53:43 -0500 Received: from [192.168.200.106] (c-24-6-5-134.hsd1.ca.comcast.net [24.6.5.134]) (authenticated bits=0) by colo.lerdorf.com (8.13.5/8.13.5/Debian-3) with ESMTP id jB6IrbD1003662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Dec 2005 10:53:38 -0800 Message-ID: <4395DE31.6060607@lerdorf.com> Date: Tue, 06 Dec 2005 10:53:37 -0800 User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: pierre.php@gmail.com CC: internals@lists.php.net, Derick Rethans References: <438E77BA.8060509@prohost.org> <1133856196.439545c4de970@webmail.jdimedia.nl> <20051206090806.407e7799@localhost.localdomain> In-Reply-To: <20051206090806.407e7799@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 5.1.2 Release Plan From: rasmus@lerdorf.com (Rasmus Lerdorf) Pierre wrote: > On Tue, 06 Dec 2005 09:03:16 +0100 > derick@php.net (Derick Rethans) wrote: > >>> * Introduce xmlwriter extension via a symlink from pecl into core >>> and as other XML extension enable it by default. >> Make sure that the licences gets switched back to the PHP license >> then... > > It is already done since last week. > > And I still do not have some good explanation about this new > requirement. It's not a new requirement. It is simply the status-quo and common sense. All the extensions we bundle are under the same license so people get a tarball with a consistent license and they don't have to wade through a license soup trying to figure out if they meet all the requirements of a bunch of different licenses. We could add extensions with different, but compatible licenses, but there would have to be an *extremely* good reason to do so. -Rasmus