In one word, no. What is it they say, with great power comes great responsibility? I am running CentOS 6 and 7 servers with php5.6.30+ on them. You are right about the situation with Suhosin - it must be compiled as it will not be included for the update.
To start you out I must tell you this is not supported and for good reasons. I will try and expand on them later...
This "works" to get you started.
The consequences of doing so are great. If you follow that guide, make sure after you have upgraded, you manually compile Suhosin.
This will show you how to compile Suhosin.
Keep in mind when you upgrade to php5.6.x there is a new way of enabling extensions - they are no longer enabled in the php.ini file. I touch on this in my Suhosin compiling post. So this means while you may be able to get that extra "php_awesome_module" installed with the remi repo, the right thing to do is compile it - then you keep just the enabling command in the /etc/php.d ini files. Looking at one of my servers now I see that I should have compiled the two cache packages and accidentally used the remi repo, so all of the instructions are in the ini files in the /etc/php.d files for them. Php5.6 parses the /etc/php.d files for enabling all of your extensions. (No more need to edit the php.ini directly at least for modules...)
I cannot emphasize enough what this upgrade path will do for your system.
DO NOT modify the remi repo files and enable php5.6 - if you do that your system will be broken beyond repair in short order. You also need to use some method of keeping the OS from updating certain packages when you do need to run yum with remi enabled. ALWAYS DO THIS MANUALLY IN YOUR YUM COMMAND! Like this:
Code:
yum --enablerepo=remi,remi-php56 install such_and such_package
This way you see what is going on and can head off problems at the cli and not later after things are all broken. And it also is required; for if you try to install anything that needs a php5.6 package to be updated or installed, the output of your yum command will be a pile of conflict errors.
You need to pay close attention to what the OS wants to update when you do enable remi in your yum statement. You will find after upgrading and depending on what sort of other repos you have installed, that you may need to exclude some updates as they may break or conflict with critical Sentora packages. I use the exclude command in the repos because I am lazy... The right thing to do is likely use yum priorities for this - but I found that to be very difficult and not guaranteed.
And don't forget. When you go to install a package with yum, if there is an accompanying php update, you will see all sorts of conflicts when you try and run yum. If one of the things in the list is a php module of some sort, you will need to manually enable remi in your yum statement as noted above and try again.
The bottom line is this. I needed the updated php just as you do for a dependency. So I took a deep breath and dove in. What the developers here will tell you and rightfully so is that by doing this, changes they make to the Sentora package may end up becoming completely broken because their expert work is based on the older, but default (and supported by back-porting) php versions that come packaged with CentOS Ubuntu or the like.
Off the top of my head, perhaps you might want to first search for doing the update with I believe it is the SCL repo? I have heard but not tested this and it may be less troublesome
. I have no data on that...
If you have specific questions, I (and perhaps others) will try and help you, but I think I gave you enough here to get the job done, or blow it up trying.
LAST WARNING --> This is not supported in the least by the developers! Good luck, and don't fret most of it sounds more intimidating than it really is in the end.
Oh, I almost forgot to mention the obvious to me and maybe not to others is you must have Sentora up and running in CentOS with its native php version BEFORE upgrading. You cannot install php5.6 and then try and install Sentora, it will not allow it.
