Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106124 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 57711 invoked from network); 1 Jul 2019 17:57:58 -0000 Received: from unknown (HELO mout.gmx.net) (212.227.17.22) by pb1.pair.com with SMTP; 1 Jul 2019 17:57:58 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1561994136; bh=9j7DaoqAIp1ia5tON773ePkOrW5St7hWVxZgFA3kSs4=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=Z0FLP+2QHWTfoOTvjPUqo5+uIFRlYFbYSjqaAYWFyQCDvWpkBBsVXy9cjH6JIwbGv P+3KzOEM1PLjuZvphPzECziThoyqGVDu9ZWjinh/bIljRaZBnWhpz44hrFgGI4Pm7g UQoN9OwYv84/cqWNUnyej47wWXO1aE7KQIsfhIMQ= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [192.168.2.144] ([79.222.32.25]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ld3t6-1iQ4Do3JMO-00iFYt; Mon, 01 Jul 2019 17:15:36 +0200 To: Peter Kokot Cc: Stanislav Malyshev , Internals References: <519a993a-98fb-8343-6565-29b8245ada63@gmx.de> <4172a1b9-ab6c-be15-9702-1fbae2a61026@fedoraproject.org> <34216fbb-626c-1acf-50ac-80b59262b7af@gmx.de> Message-ID: Date: Mon, 1 Jul 2019 17:15:36 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:6Z2k0UNeKCVhGH3ijTtuA9mLsDdsYiCWtXfd4gXqIqKlzDTTb35 iA9MWGrcJoNa+iOxJn3UCoMr3tkhsVpEI1VciE+q40Ka8Q7pD/Z8pGhEDG760tc/nAqu/X/ adRFQbQNBrHlsV1oco6fX/W7cT1g1sC4Cuam4aanKNWbYXf8P3Tdw8bzuDzwq+DxVy12Iy/ bvqCn2lXmebal43+mIAEA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:5U1VeGNNq3M=:oJ3uxJZ1hCz6U02uE+tU3o RPkOrYvGQpARHSAd0sp46aomihViLKkODvyKtXJbsxoI8yzX93OvkkpPdN+XGdU8tGBK2+60H bTuNT7Rc5YDePr2ku1XQczPPv5Ixx88yqPzb1QpPBnrY11sUOzwOQi11pjErmISg20zAqLwPA nBOB7v6XeVAVe0lzHKwUVTLAZs1ALC6DS7aUtT26VJ3y2AxjctV0VAUdc9k7o0N0O8zPF0Tf6 +RnIUxVvs4MTiSCy9oPA6UOkN7NjhCHbEQquu+EQp9thGR59tUQ4O2NhipfBsmdQyHBYoB/+Y wXXoUhuFAa4ZWgprFiVYID2FjIoTD6hhVQ7lBWBTrYjnMuGzCsitN6wEZBvIE0EfMA2fFfhFf a6/3DizHrcMqBrYpkd8zi9FrO6B4PyAziwX13HHOUTvaytYEgo87MydP6SkiSNSxrXVmJu+6N 5cWtqX9zcmU9n41RerMa0jSU2JdS9l9Z2PI2M2RyrGYgtn40DY6ReOCbqBGP9QV8yU36grP+5 xAmuSqfdHCFeZ6yo+wxTKY8EHFmk6UcIELVWuj05HOxlCZVl8OuwvAoM2s0BY+Cc+HSlh1sVJ XlbfeqDtqgSU7WsO5Li3YpeGYxTlJyeQ9IgKgMbmIxCCIGqO3Cz8lssFVwBfHQY3UyN0CSKZA zrjVjcxqjqXMcDnwkOfRuVpeTbfNDmNuDcxBcoIFJquaas+9rDrWq69W3/5AmmK3KTkh5DRCZ jd/UuIitOSLdTQKVCLJguvXaloNA4VDPt3ojxrD3v9He0juo9B2MkGciy/EzXEoLv6567hRmt EIwgCVInAbjvA606UEGeVMRjmPSxWk/gSmkmQPESGLkGFG7o3lZYlC1FqRvPoWQWQc2N7keqe N4wwsPg9xldwHYeAKIlgdzqNCi63oyhQ0kgxrXNdHydLCzmbrC11mU6fbSbYA8En8FvjID/u0 k099xxrc5TO2EPmFAMTSiGJewDGM8u+RYOkx1OY1YIYIc3jZa15+XiBbo1UwL9NUaIWzaPJ5T WlV9mIJ8ZG7R1aJEB1DZMK1+5CvoqkAuqMqZwU3TxasVKR7VPJIAE35Wldo1xTJggQ8JplGAi 6E1Qx7wdpSeIciEcdtt0HiMctd7dOJBLGXC Subject: Re: [PHP-DEV] What to do with ext/xmlrpc? From: cmbecker69@gmx.de ("Christoph M. Becker") On 29.06.2019 at 18:31, Peter Kokot wrote: > On Fri, 28 Jun 2019 at 17:57, Christoph M. Becker wr= ote: >> >> On 28.06.2019 at 17:49, Peter Kokot wrote: >> >>> On Thu, 10 Jan 2019 at 19:43, Stanislav Malyshev = wrote: >>>> >>>>> ext/imap should follow the same road. >>>>> >>>>> BTW, if we want to keep this extension, we need to consider the bund= led >>>>> library as a fork, maintained by US (and drop support to build using= the >>>>> system library, if present) >>>>> >>>>> So, any new volunteer to maintain this extension, will also have to >>>>> maintain the library. >>>> >>>> This looks unlikely, so we shouldn't count on it happening. I think w= e >>>> should just move them to PECL and if somebody shows up, we can always >>>> move it back. >>> >>> Hello, sorry for bumping this one. Is the ext/xmlrpc extension also on >>> the list to be unbundled maybe for PHP-7.4? >> >> AFAIK, it isn't. Sorry for not having pursued this. > > Then I can create an RFC to unbundle it from the core and move it > together with the libxmlrpc library fork into PECL. Having > unmaintained extensions in the core and marked as experimental for the > last 18 years is not good I think. Is there enough time to do all this > until July 22nd (7.4 feature freeze)? I think it's too late to start an RFC targeting PHP 7.4, since there is a minimum of two weeks for discussion and two weeks for voting. =2D- Christoph M. Becker