Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107207 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 94474 invoked from network); 18 Sep 2019 17:16:38 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 18 Sep 2019 17:16:38 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id D67C92CFFB9 for ; Wed, 18 Sep 2019 07:54:00 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS31103 84.19.160.0/19 X-Spam-Virus: No Received: from mail.experimentalworks.net (mail.experimentalworks.net [84.19.169.162]) by php-smtp3.php.net (Postfix) with ESMTP for ; Wed, 18 Sep 2019 07:54:00 -0700 (PDT) Received: from [192.168.2.46] (ppp-188-174-61-13.dynamic.mnet-online.de [188.174.61.13]) by mail.experimentalworks.net (Postfix) with ESMTPSA id C9E056CAFD; Wed, 18 Sep 2019 16:53:58 +0200 (CEST) Date: Wed, 18 Sep 2019 16:53:55 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: <61ab41b2e7eb74c23bc0dc4a307d1045863966fc.camel@schlueters.de> <51d2093d-7ad5-c50e-0a33-1b088b891223@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: "Christoph M. Becker" ,Arnold Daniels ,internals@lists.php.net,Anatoliy Belsky Message-ID: X-Envelope-From: Subject: Re: [PHP-DEV] Changing PECL signup flow. From: johannes@schlueters.de (=?ISO-8859-1?Q?Johannes_Schl=FCter?=) On September 18, 2019 3:32:38 PM GMT+02:00, "Christoph M=2E Becker" wrote: >On 18=2E09=2E2019 at 15:22, Johannes Schl=C3=BCter wrote: > >> The Windows builds are also a relevant factor in the discussions >> regarding the PECL site=2E Afaik (Anatoliy and others know better than >> me) packages uploaded to the pecl site are being built in the same >> setup as our official PHP runtime Windows builds=2E > >The PECL builds are done on another VM than the Windows builds=2E Good to know=2E If not done another got thing is if each build runs in its= own container or from a clean VM snapshot or whatever capabilities there a= re for Windows =2E=2E=2E Anyways different topic in itself=2E Just came to mind while thinking abou= t the pickle tool=2E And possible future paths=2E=20 One thought in my head (also away from the initial question) is also wheth= er we could provide Linux builds - since removing TSRM it came closer to be= ing feasible to have a stable common interface for 95% of extensions=2E (Th= ere are the ones which go deep =2E=2E=2E but for most the only thing they h= ave to interact with is a zval which is relatively stable and a class_entry= +zend_object where most things should be wrapable behind accessor functions= with stable API) If we just need one single build with static dependencies= covering most systems (some (g)libc dependency =2E=2E=2E while glibc has v= ersions APIs and quite good compatibility these days) this could cover the = 80/20 case=2E Or is ffi the big push for those 95% making pecl actually mostly obsolete,= solving the whole thing that way round? (I admit - I never looked at FFI) = Then only extensions "going deep" (xdebug, mysqlnd stuff, runkit-like, =2E= =2E=2E) need some distribution channel, while ffi code could use packagist/= composer=2E johannes