Hi,
If you miss the news
https://framework.zend.com/blog/2019-04-17-announcing-laminas.html
In short, Zend is dead, and moved to Laminas
In composer.json, all ZF libraries are replaced by their
Laminas counterpart, and works thanks to a bridge (dedicated autoloader)
Don't know yet what is the plan... for 81 packages
- create new packages and retire old ones
OR
- update packages to switch to new sources
Any idea welcome
Remi
Hi all,
My PHP apps(s) depend on php-libsodium or php-sodium. So far it is not
possible to deploy on RHEL 8 / CentOS 8 due to [1]. I'm wondering if
there is a recommended approach to build either php-sodium or
php-libsodium in such a way that when [1] is resolved and php-sodium is
available from EPEL the upgrade will be smooth? I try to avoid Remi's
repo as it will be difficult to 'unuse' it later on when EPEL is
"fixed". libsodium itself is already available in EPEL.
I can see three possible approaches:
1. Build PECL php-libsodium for PHP 7.2 and 7.3 on CentOS 8, this seems
to be supported at least by the PECL module itself;
2. Take the CentOS PHP source RPM/spec and enable the sodium module and
rebuild the PHP package.
3. Take the ext/sodium code from the CentOS RPM source code and extract
it as a separate module and build that.
I tried 2, but it conflicts with the CentOS modules, I probably do
something wrong...
Not sure what is the best approach here... Any advice?
Thanks!
Regards,
François
[1] https://pagure.io/epel/issue/75
