Re: What to do with ext/xmlrpc?
| From: | Peter Kokot | Date: | Sat, 29 Jun 2019 16:31:13 +0000 |
| Subject: | Re: What to do with ext/xmlrpc? | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106112@lists.php.net to get a copy of this message | ||
On Fri, 28 Jun 2019 at 17:57, Christoph M. Becker <cmbecker69@gmx.de> wrote:
>
> On 28.06.2019 at 17:49, Peter Kokot wrote:
>
> > On Thu, 10 Jan 2019 at 19:43, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> >>
> >>> ext/imap should follow the same road.
> >>>
> >>> BTW, if we want to keep this extension, we need to consider the bundled
> >>> 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 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.
>
> --
> Christoph M. Becker
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)?
--
Peter Kokot