Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106112 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 94428 invoked from network); 29 Jun 2019 19:14:13 -0000 Received: from unknown (HELO mail-ot1-f43.google.com) (209.85.210.43) by pb1.pair.com with SMTP; 29 Jun 2019 19:14:13 -0000 Received: by mail-ot1-f43.google.com with SMTP id e8so9188177otl.7 for ; Sat, 29 Jun 2019 09:31:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cBaKhO5qaKM9j/NpeHycSBkad5IGtaG5JngnRJZovp4=; b=vK7UQuekCVNiVqzbh7A6miMxCULeuo9f2y7YzTWKpoqE5Jf+3VJSozi5M3YjcjESzv 20yITXuBqoNcuBoSJL7asgeY3m7zzLFdDGiFoDLX1I64ph5IYZNB6Utnk9zZTgm3TTLR mNdCqKkzvt0knvlN3drSmbQPoWc4N4ScLYJW6i6kVmSeLio2YP41QjdyuGWJGgQEVseZ 8bHu6k/NyZGdt8MUy0BoDP7bnz8oCcK+tR8lV91F9m9aFbX6/BT9dXxMpjPzyekXLLqq /mQl1HyXmVOJoxIKQATOUfUDjqqPO8kZgQq9yUJOzpfXNIrVqWlX6uSMYEW34QNEY4Am M9vQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cBaKhO5qaKM9j/NpeHycSBkad5IGtaG5JngnRJZovp4=; b=fQcjDoKzGWhCWmCHYzuZ0KenuJRBIUPnFWZoMU9KdlwVP9kokHnS1EAmgdjH/c04vJ ubnJ/Xad3SPOTaRqMHGSTvOLO6TAHEFTPijmdaQ1+gGr7XQthLOS9qCNhenSD1ipRfTo 33RSQu3LSXMg8qTDAC+aNl4tmxwVkzGMs+1eR0hRGFL2ZW+FlkKcnSUcCwHp/iDYC4Gf 1b3unaCxXldGt6//+zDlXuNZp21DJAuwjMX8i0fS+z0AF8wrqfEagdRX+9YJjuBAZu+j JhPiVw8mF7guKGdrMZX8jEtUL6YCgmMAaOCdn1ZtdaYE/2FcH+FBR82dce6b143UaXOJ rulQ== X-Gm-Message-State: APjAAAXRiOgegLpkc0dFsOAZ6DQ8zgz9d+oMIEoXm79ad3J5LwYHM499 bLtyFr5ybaJNY4tVk0mKXEQli7Y4Z7aLCE2QqB4= X-Google-Smtp-Source: APXvYqxQmft7lQbYyYyVPiNiwUpvY1m48QwJvkgihEoHAMYkOxfx9gturn/dMkPCt3eQIdEhIwp4J+YxXomc4fDE31E= X-Received: by 2002:a9d:7988:: with SMTP id h8mr12700926otm.301.1561825884371; Sat, 29 Jun 2019 09:31:24 -0700 (PDT) MIME-Version: 1.0 References: <519a993a-98fb-8343-6565-29b8245ada63@gmx.de> <4172a1b9-ab6c-be15-9702-1fbae2a61026@fedoraproject.org> <34216fbb-626c-1acf-50ac-80b59262b7af@gmx.de> In-Reply-To: <34216fbb-626c-1acf-50ac-80b59262b7af@gmx.de> Date: Sat, 29 Jun 2019 18:31:13 +0200 Message-ID: To: "Christoph M. Becker" Cc: Stanislav Malyshev , Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] What to do with ext/xmlrpc? From: peterkokot@gmail.com (Peter Kokot) On Fri, 28 Jun 2019 at 17:57, Christoph M. Becker wrote: > > 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 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