# Status of pickle? - Thread: https://externals.io/message/104982 - Original archive: https://news-web.php.net/php.internals/104982 - Started by Levi Morrison on 2019-03-28T15:39:33+00:00 - Messages: 5 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #104982 — Levi Morrison — 2019-03-28T15:39:33+00:00 URL: https://externals.io/message/104982#104982 I was reviewing the options for installing extensions on a per-project basis. The most recent effort I have found was pickle. Can someone more knowledgeable chime in on the status of the project? I'm also interested in why it hasn't gained more traction. --- ## #104983 — Joe Watkins — 2019-03-28T17:02:15+00:00 URL: https://externals.io/message/104982#104983 Morning Levi, For me, as author of many extensions, pickle becomes valuable at the point when composer supports it and we have another route to deployment built into composer. Currently, there is no remarkable difference between using pecl or pickle to build, except pecl is available everywhere, and pickle is only available after an additional dep in composer.json. I'm not sure of the exact reasons why the project lost traction, there seemed to be some disagreement about how to move forward between developers of pickle and composer. Cheers Joe > I was reviewing the options for installing extensions on a per-project > basis. The most recent effort I have found was pickle. Can someone > more knowledgeable chime in on the status of the project? I'm also > interested in why it hasn't gained more traction. --- ## #104986 — Pierre Joye — 2019-03-29T04:29:22+00:00 URL: https://externals.io/message/104982#104986 > I was reviewing the options for installing extensions on a per-project > basis. The most recent effort I have found was pickle. Can someone > more knowledgeable chime in on the status of the project? I'm also > interested in why it hasn't gained more traction. We did not push it hard. Also it is mostly features complete but a packagist for extensions. The latter is not a must as pickle works exactly like composer, it can install ext from any sources, git, archives, pecl.php.net or files. I provided a PR a while ago to integrate it to composer, but the composer team wanted it using another way. I still do not know what would be the best way but it should not be too complicated. On a side note, pickle is not related to php.net. :) best, --- ## #105018 — johannes@schlueters.de — 2019-03-31T01:20:26+00:00 URL: https://externals.io/message/104982#105018 > 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 --- ## #105019 — Pierre Joye — 2019-03-31T04:13:14+00:00 URL: https://externals.io/message/104982#105019 Hi, On Sun, Mar 31, 2019, 8:20 AM Johannes Schlüter wrote: > > > […] > > 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. Right, and on linux it is almost a no brainers if no deps are used. Mac is trickier, windows is easy once you have VC and the SDK. 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. > containers, app pool or phpenv could be used indeed. It is however out of the scope of pickle. It should straightforward to use pickle in any of them. Best, Pierre