php-devel September 2017

php-devel@lists.fedoraproject.org

3 participants
3 discussions

[HEADS-UP] PHP 7.2 in rawhide next week
by Remi Collet 03 Oct '17

03 Oct '17

Hi, I plan to build PHP 7.2.0RC3 in rawhide next week, so we'll have a lot of time to ensure everything is ok before F28 is branched. Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=22144004 Work done in private branch https://src.fedoraproject.org/cgit/rpms/php.git/log/?h=private-php72 All extensions are already compatible, so I will also rebuild them. Notice: the mcrypt extension is no more provided I will consider later if we need the php-pecl-mcrypt package (I heartly hope we can avoid it) Remi

1 1

dealing with (lib)sodium migration EPEL/Fedora
by François Kooman 28 Sep '17

28 Sep '17

Hi, Currently php-libsodium 1.x (no longer maintained upstream) is packaged for EPEL and all releases of Fedora. This version makes the libsodium calls available with the \Sodium namespace. This will be changed when PHP 7.2 is released and the calls will use sodium_ instead of the namespace. A php-libsodium 2.x library is available (maintained), only available for PHP >= 7.0 that also uses the sodium_ convention. Ideally we'd have a polyfill that takes care of these cases. There is one, but not sufficient for the EPEL/Fedora case [1]. It rewrites the \Sodium calls to the PHP 7.2 calls, which only works with php-libsodium-2.x which is not packaged. I'm thinking of writing my own polyfill that will expose \Sodium and try to fallback to sodium_ if available or just "forward" to \Sodium calls if not. What do you guys think? Is there any path to update to php-libsodium 2.x in Fedora or is the plan to wait it out for PHP 7.2? I assume PHP 7.2 will be part of RHEL 8, so that would take care of that problem as well ;) Cheers, François [1] https://github.com/mollie/polyfill-libsodium

2 3

Fedora 27, httpd in thread mode by default, need for ZTS php modules
by Remi Collet 27 Sep '17

27 Sep '17

Hi, Starting with Fedora 27, the Apache Webserver is now configured by default to use event MPM (threaded) Which means ZTS mod_php will be used. Some packaged extensions only provide the NTS build, so won't be available in web context (using httpd + mod_php), but only when - php-fpm is used - httpd is configured to used prefork MPM (not threaded) So, probably worth investigating if the ZTS module can be enabled during the build. Example, for ssh2 extension: http://pkgs.fedoraproject.org/cgit/rpms/php-pecl-ssh2.git/diff/php-pecl-ssh… Notice, mod_php in ZTS mode is not recommended per upstream documentation: http://php.net/manual/en/install.unix.apache2.php http://php.net/manual/en/faq.installation.php#faq.installation.apache2 So php-fpm should be preferred. So web applications should not require "php" (or mod_php) but php(httpd) instead (provided by both php and php-fpm packages). Remi.

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

php-devel September 2017