Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121986
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-1178-geeaf0069a7-fm-20231114.001-geeaf0069
MIME-Version: 1.0
Message-ID: <b6a8095d-a9d0-494a-bfa9-70cff24417dc@app.fastmail.com>
In-Reply-To: <0b25cbe2-1986-c499-defc-a556114853df@php.net>
References: <8d4bcca5-a2ce-5ee1-1aed-02076539433a@php.net>
 <c6af7028-a731-4087-8245-40e543d05eb8@wikimedia.org>
 <0b25cbe2-1986-c499-defc-a556114853df@php.net>
Date: Mon, 11 Dec 2023 16:20:45 +0000
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] New "PECL"
From: larry@garfieldtech.com ("Larry Garfield")

On Mon, Dec 11, 2023, at 9:46 AM, Derick Rethans wrote:

> Yeah, I understand. And I feel the same. But if there is no registry (a 
> goal), then there is no way to find out which of your extension version 
> support a specific PHP version, without checking every tag in your 
> repository. That's not going to be fast.
>
> cheers,
> Derick

See, I think I disagree on this point.  Having a registry is table-stakes for package managers these days.  Composer, npm/yarn, whatever Python does this week, Cargo, Bundle, Maven/Gradle... a packager isn't complete without a registry.  The one exception is Go, and its approach is... just a mess, frankly.

Whether PECLtng piggybacks on Packagist, self-hosts using something like Satis, or does a home-grown thing, I don't think a neo-PECL without a registry is a viable and sustainable way forward.  That needs to be in the initial design.

--Larry Garfield