python 2 -> 3** An example is that the previous version of Drupal (7) runs perfectly on php7 with dozens of addon modules (one of my test cases). -- Jimmy On Sat, Dec 12, 2015 at 11:37 PM, Jimmy Berry <jimmy@boombatower.com> wrote:
Unlike python 2 -> 2. php 5 -> 7 does not have major incompatibilities that should affect most projects. Short of some horrendous syntactically incorrect code that doesn't run in php 5 anyway that php 7 will complain about, there are only additional features, under the hood overhaul, and removal of features that had been deprecated for ages (like insecure mysql extensions).
All of the personal projects I use were able to run on php 7 and generally seems to be the consensus online. If we want both to be installable alongside eachother then the php7 and perhaps php5 package needs to be updated to not share the same path. I do not think this is necessary and for something like Tumbleweed it seems reasonable to attempt and make it the default (obviously exploring for issues).
The *requires changes I proposed will need to be made regardless since they make it impossible to use the compatible packages with php7 (held up waiting for resolution of 120+ build failures so it will be easier to verify).
In general people should be able to just upgrade to php7. They went the more aggressive, break stuff route, with php6 and due to backlash and other problems they abandon that approach. As such php 7 should be generally compatible with both php code and extensions.
-- Jimmy
On Sat, Dec 12, 2015 at 10:34 AM, Bruno Friedmann <bruno@ioda-net.ch> wrote:
On Wednesday 09 December 2015 05.01:17 Jimmy Berry wrote:
I attempted to install the php7 package and noticed it does not replace/conflict with php5 and so it runs into a file conflict when installing. I added obsoletes to php7 package which behaves as desired. - https://build.opensuse.org/request/show/348020
I am not sure if there is a clean way to auto update all php5* packages with php7* packages where applicable.
Next I noticed a number of php applications will be removed when updated to php7 which is due to hard dependency on php5 package. Many of the packages will work fine on php7 (or may in the future) and so I am working on changing them to php-foo virtual packages instead of php5-foo.
I wrote a script to try and detect and fix basic *Require statements in .spec files.
Will eventually create submit requests similar to: - https://build.opensuse.org/request/show/348017 - https://build.opensuse.org/request/show/348012
All work will be done in: - https://build.opensuse.org/project/show/home:boombatower:branches:server:php...
Just a heads up in case others are working on this or considering it. Once I have an automated run I am happy with my plan is to do a fair bit of manual inspection and hopefully run a script to ensure same platforms fail to build as parent project and then run submit requests.
Any suggests are appreciated.
-- Jimmy
Just a question, before php7 will be considered as first choice, php5 will stay at least one or two years. Big projects will not be able to migrate quickly and would like to stay on php5.
Isn't there a simple way to have update-alternatives packaging as it's done for python2 / python3 especially that php5 in /etc var/lib and so is already there, it can't have conflict with php7 derivative.
Just a through
--
Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch
openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org