On 02/01/2014 15:36, Tanstaafl wrote: > On 2014-01-02 8:15 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote: >> On 02/01/2014 14:46, Tanstaafl wrote: >>> Hi all, >>> >>> I have a VM running in the cloud that has an old web/php app (10+ years >>> old, believe it or not), that still runs fine on apache 2.2.25, but I >>> pinned php to 5.3 some time ago. >>> >>> Does anyone see any big potential gotchas (major changes) with php 5.4, >>> or even 5.5, if I were to upgrade it? > >> Impossible to say without seeing your php code. Potentially there are >> many changes. >> >> You'd be better off doing the heavy lifting yourself first: >> >> 1. read all the changelogs >> 2. run it in a staging vm with php5.5 and see what happens > > Actually, I was just thinking of doing #2 on the dev server (no dev > going on, but I had this set up some time ago when we moved the > production server to linode, so now at least I can test things without > breaking the production system), and if it breaks, just downgrade back > to 5.3... > > That assumes, of course... > > Is php difficult to downgrade after an upgrade?
I don't see why not, all three are in the tree and supported (and it's not glibc) It might take a few goes through the emerge && depclean cycle to get it back to a working state but it should all sort out eventually. And you can always quickpkg things that get upgraded before doing the emerge. Even better, use a VM and snapshot it. -- Alan McKinnon alan.mckin...@gmail.com
