| Summary: | [RFE] include PHP 5.6+ and all the dependent packages based on the PHP version | ||
|---|---|---|---|
| Product: | Red Hat Software Collections | Reporter: | Ash Westbrook <awestbro> |
| Component: | rh-php56 | Assignee: | Remi Collet <rcollet> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rh-php56 | CC: | hhorak, jorton |
| Target Milestone: | alpha | Keywords: | FutureFeature |
| Target Release: | 2.2 | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-22 14:22:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
> We tried to follow the instructions and made php5.6 available for use, but > found that the dependent php packages php-mcrypt.x86_64 php-dom php-pecl-apc > are 5.3.X or 5.4 versions along with these bringing back php-common 5.3.3 php-mcrypt if not part of RHEL (have never be). Probably user is confused because thay use the package available in EPEL. As Software Collection are not allowed in Fedora (so EPEL), you can look at https://www.softwarecollections.org/en/scls/remi/php56more/ This is a community repository, no support, as EPEL. About mcrypt I recommend to read http://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcrypt php-pecl-apc have no version for PHP >= 5.4 Project is dead. For opcode cache, see php-opcache which is part of the collection For user data cache, see php-pecl-apcu which is a drop-in replacement of APC (without opcode cache). This is part of php56more repository. About: php-dom, the package is rh-php56-php-xml But, like for all extensions, "yum install rh-php56-php<extname>" should work. Please do not rely on package name as packages layout may change > ...they suggested PHP 5.6 is available in the Red Hat Software Collections
> repository, but using this needs symlink which is not a desired option and
> whenever there is reboot, this collection link disappears...
Can you please explain this issue.
Using (it you can remove system php)
ln -s /opt/rh/rh-php56/root/usr/bin/php /usr/bin/php
This should be permanent across reboot.
It's not clear exactly what is being requested here which is not already present in RHSCL rh-php56. Please re-open and clarify if there is an outstanding requirement from the customer, other than the issues Remi already addressed above (we are not planning to ship mcrypt or apc in RHSCL). |
1. Proposed title of this feature request USPTO Drupal Package 2. What is the nature and description of the request? RHN does not have a clean channel for RHEL7 with PHP5.6, so we had a CASE 01574555 with RedHat and they suggested PHP 5.6 is available in the Red Hat Software Collections repository, but using this needs symlink which is not a desired option and whenever there is reboot, this collection link disappears and we will need to have a script at the startup to make it available even after reboot. We tried to follow the instructions and made php5.6 available for use, but found that the dependent php packages php-mcrypt.x86_64 php-dom php-pecl-apc are 5.3.X or 5.4 versions along with these bringing back php-common 5.3.3 So, we would like to have RHEL7 packaged with PHP 5.6+ and all the dependent packages listed below in this document based on the PHP version. 3. Why is this required? (List the business requirements here) These are requirements are mainly for our improving Drupal CMS customized baking (Page Generation). With these updated packages, we can take advantage of the features they offer. With the updated packages, we can drastically cut down the total time of entire site regeneration process. Also we have plans to upgrade Drupal from current 7.XX to 8.XX and minimum PHP version of Drupal 8 has been raised to 5.5.9. In addition, the current PHP version that USPTO is using, PHP 5.3, has well passed its end of life and it is currently not maintained. http://php.net/supported-versions.php 4. How would you like to achieve this? (List the functional requirements here) Once the channel is made available on USPTO RHN, we will request our Server Operations Support group to install the required packages on the Apache server(We have an internal process(SDAP) to request New server and packages required) 5. For each functional requirement listed in question 5, specify how Red Hat and you can test to confirm the requirement is successfully implemented. These are requirements are mainly for our improving Drupal customized baking (Page Generation). With these updated packages, we can take advantage of the features they offer. After successful we can provide the benchmarking statistics on the improvements. 6. Any specific timeline dependencies? As soon as possible. 7. List any affected packages or components. php php-cli php-common php-gd php-pdo php-dom php-mbstring php-mysql php-ldap php-pear php-devel php-mcrypt php-posix php55w-pecl-memcache zlib-devel On Browser php.info should have the following displayed as installed php –m [PHP Modules] Apc bz2 calendar Core ctype curl date dom ereg exif fileinfo filter ftp gd gettext gmp hash iconv json ldap libxml mbstring mcrypt geocache mysql mysqli openssl pcntl pcre PDO pdo_mysql pdo_sqlite Phar posix readline Reflection session shmop SimpleXML sockets SPL sqlite3 standard sysvmsg sysvsem sysvshm tokenizer wddx xml xmlreader xmlwriter xsl zip zlib 9. Are you be able to assist in testing this functionality if implemented? Yes, we will be testing our Drupal CMS system with these improved versions of packages