Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121928
MIME-Version: 1.0
References: <8d4bcca5-a2ce-5ee1-1aed-02076539433a@php.net>
In-Reply-To: <8d4bcca5-a2ce-5ee1-1aed-02076539433a@php.net>
Date: Tue, 5 Dec 2023 22:13:40 +0700
Message-ID: <CAEZPtU40BbGCYcf4GugLsaDbRp98wr4bTNXYd=cp=XuKxRSyMg@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009f1741060bc4ae61"
Subject: Re: [PHP-DEV] New "PECL"
From: pierre.php@gmail.com (Pierre Joye)

--0000000000009f1741060bc4ae61
Content-Type: text/plain; charset="UTF-8"

Hi Derick,

On Tue, Dec 5, 2023, 8:45 PM Derick Rethans <derick@php.net> wrote:

> Hi there!
>
> Within the PHP Foundation, we have been talking for a while as what to
> do with PECL, and its website.
>
> The code is old, and hard to maintain. And the database is full of
> mojibake. It is also an outdated method of installing things, especially
> because userland code is so much easier to handle through Composer.
>
> Through the Sovereign Tech Fund (https://www.sovereigntechfund.de/) the
> Foundation has acquired some funding to improve this situation.
>
> Hence, to start of replacing PECL with something applicable for this
> decade, we started working on a requirements document:
>
>
> https://docs.google.com/document/d/1_N0E9xo3jn9aKrIZHIbTYaY5lXw71BpSO6-it4cRpDo
>
> In this first stage, we would like to invite you in commenting on the
> document (either inline, or here).
>
> Please keep in mind that this is a requirements document, and should not
> contain either design or implementation details. Once we have thought
> about these details as well, this will be turned into an RFC.



You may mention https://github.com/FriendsOfPHP/pickle

which supports pecl.php.net pear format,  composer like support, and
conversion to composer format.

I did a website as well as a test bed and we had a long with the composer
team what would be the best way to integrate it. That's something that
became possible with composer 2.x, which now widely used. Similarly we
discussed the idea to create a packagist dedicated to extensions.

That would be, imo, the best option to date.


The current code may need some updates for php8 but nothing difficult or
requiring big changes.


best,
Pierre

--0000000000009f1741060bc4ae61--