Hi Richard, > I purchased the above for a client to install IPS on the server. It is > complaining about cURL extension being less than 7.36. Is it possible to > update this particular component?
This is a bit tricky. Curl is a command line utility and it's provided by the OS. PHP can be compiled with Curl support, in which case it then builds either a PHP extension or a built in component that provides Curl support from within PHP. As if you couldn't call Curl via system() call without problems either. So long story short: PHP uses the Curl that was present on the box when PHP was built. On EL6 this is v7.19 and on EL7 this is v7.29. I don't really see why anything would need a specific version of Curl. Because as long as it's patched it simply allows you to make HTTPS GET and POST requests via a CLI. There is not much meaningful difference in functionality between the Curl versions that I'm aware of. Even Epel don't mess with it and don't provide a newer Curl. > Also, they recommend MySQL 5.6.0. Will this be available at some stage? On 5209R this is less of a problem. We're using MariaDB-5.5 there, which is equal enough to MySQL-5.5. There is a MariaDB-10.0 series, which is built on the 5.5 series and backports features from MySQL-5.6. MariaDB 10.2 Series has features from MySQL 5.6 & 5.7, and entirely new features not found anywhere else yet. But that's in development and not yet fully stable. In my experience we can install MariaDB 10.0 on a 5209R without breaking anything. I'm still considering making that one available as a free PKG for 5209R, but it requires some omissions in our BlueOnyx YUM repository Package list that I haven't yet figured out entirely. So on 5209R in the short term we can cover this by providing MariaDB 10.0. On any older BlueOnyx (5106R, 5107R, 5108R, 5207R and 5208R) replacing MySQL with another version is a big "Hell, no!"-issue. Both the onboard PHP and the Solarspeed PHP are compiled against the onboard MySQL. Likewise a Perl module that deals with access of Perl to MySQL is compiled against the "stock" MySQL. Once you replace MySQL with a different version, all hell breaks loose and anything that needs access to MySQL will throw errors and fails to work. The MySQL-5.5 and MySQL-5.6 PKGs for EL5 and EL6 based BlueOnyx provide not only the newer MySQL, but also the php-mysql RPM to "repair" the onboard PHP and the perl-mysql-DBD and perl-mysql-DBI that can work with that version of MySQL. The Solarspeed PHP for EL5 and EL6 also have provisions to work both with the onboard MySQL *and* the one from the MySQL PKG out of the store that matches that platform. However: This doubles the compile time and triples the product testing. Because I need to compile twice (once against the "stock" MySQL and once against the upgraded one). And during testing I need to reinstall/uninstall the MySQL PKG and test the updated PHP against each. If I would throw MySQL-5.6 into the mix, compile time would triple and testing would get so bloody lengthy that it's no fun at all. Hence I'd say: Depends. For 5106R there will not be a newer MySQL, as it'll be EOL in six months (31st March 2017) anyway. For 5107R, 5108R, 5207R and 5208R I might consider it within the next half year. Depending on what CentOS-6.9 brings, which probably will most likely be the last full update of CentOS 6 anyway (Q2, 2017). EOL for that will be 30th Nov 2020. I *might* consider dropping MySQL-5.5 support from the shop provided PHP for EL6 and to replace it with MySQL-5.6 support in the somewhat longer run. But short term it's too complicated to tackle. -- With best regards Michael Stauber _______________________________________________ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
