Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106091
To: Peter Kokot <peterkokot@gmail.com>,
 Stanislav Malyshev <smalyshev@gmail.com>
Cc: Internals <internals@lists.php.net>
References: <519a993a-98fb-8343-6565-29b8245ada63@gmx.de>
 <4172a1b9-ab6c-be15-9702-1fbae2a61026@fedoraproject.org>
 <ffb139e3-f1ae-aa3d-8f56-6eb9d68d54aa@gmail.com>
 <CAAfnsFVf=0oS23+BcQOUMrUNbRq-JrhTv4n25AJT1THnQj0o=w@mail.gmail.com>
Message-ID: <34216fbb-626c-1acf-50ac-80b59262b7af@gmx.de>
Date: Fri, 28 Jun 2019 17:57:49 +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: <CAAfnsFVf=0oS23+BcQOUMrUNbRq-JrhTv4n25AJT1THnQj0o=w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] What to do with ext/xmlrpc?
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 28.06.2019 at 17:49, Peter Kokot wrote:

> On Thu, 10 Jan 2019 at 19:43, Stanislav Malyshev <smalyshev@gmail.com> w=
rote:
>>
>>> ext/imap should follow the same road.
>>>
>>> BTW, if we want to keep this extension, we need to consider the bundle=
d
>>> library as a fork, maintained by US (and drop support to build using t=
he
>>> 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 we
>> 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.

=2D-
Christoph M. Becker