Hi,
For libraries, PEAR (system wide installer) was replaced
by composer (dependencies resolver).
For extension, PECL is going to be replaced by PIE
See: https://github.com/php/pie
The https://pear.php.net/ and https://pecl.php.net/ websites (forges)
will probably disappear in the near feature.
php-pear sources are probably going to be unmaintained and can
become unusable because of lack of compatibility with newer PHP (9.x)
Projects registry:
- For Libraries: https://packagist.org/
- For extensions: https://packagist.org/extensions
I already have a PIE package available in my repository (version 0.1.0)
https://git.remirepo.net/cgit/rpms/pie.git/
(this is a bundle everything package)
Packaging PoV.
No big changes, as "pecl" is already an optional runtime dependency
only used to populate its system database.
We will be able later to simplify packaging
- no need to install the package.xml in %{pecl_xmldir}
- no need for doc in %{pecl_docdir}, switching to standard way
- no need for tests in %{pecl_testdir}
Package name
Like for library, using php-<vendor>-<project> will work especially
as lot of extensions will be registered in the <pecl> vendor namespace
so resulting to the same name (ex: php-pecl-apcu)
As we have virtual provide of php-composer(vendor/project)
we can add php-pie(vendor/project).
Notice: php-<extname> is the main name used for dependency
allowing to track extension moving in or out of php-src
(ex json merged in php, pspell removed and moved to pecl)
Comments and feedback very welcome
Remi
