Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105018 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 94042 invoked from network); 31 Mar 2019 04:26:01 -0000 Received: from unknown (HELO mail.experimentalworks.net) (84.19.169.162) by pb1.pair.com with SMTP; 31 Mar 2019 04:26:01 -0000 Received: from kuechenschabe.fritz.box (ppp-188-174-56-99.dynamic.mnet-online.de [188.174.56.99]) by mail.experimentalworks.net (Postfix) with ESMTPSA id 7967946424; Sun, 31 Mar 2019 03:20:31 +0200 (CEST) Message-ID: <1553995226.3484.14.camel@schlueters.de> To: Pierre Joye , Levi Morrison Cc: PHP internals Date: Sun, 31 Mar 2019 03:20:26 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Status of pickle? From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Fr, 2019-03-29 at 11:29 +0700, Pierre Joye wrote: > On a side note, pickle is not related to php.net. :) > Considering that we're kicking the pecl (pear) installer out we should provide an alternative. pickle might be one alternative, teaching people to do wget+phpize+configure+make install might be another. One thing which conflicts with composer is that PHP extensions aren't loaded "per project" but per setup and the PHP setup used to run composer isn't necessarily the one used for running the application (for one composer typically is run from CLI, applications use fpm or similar, but there might also be a deploy pipeline with different machines in between, ...) But maybe a 80% solution (i.e. working on many developer setups and extendable to be plugged into complexer environments) is still useful, or a solution building docker images with userspace+extension dependencies per project. johannes