Re: Non-conflicting PHP 5 and 7 builds
| From: | Jordan Gigov | Date: | Sun, 04 Sep 2016 07:57:33 +0000 |
| Subject: | Re: Non-conflicting PHP 5 and 7 builds | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95610@lists.php.net to get a copy of this message | ||
I can see your argument for using prefix, but that would not provide a
solution to package maintainers who may want to give their users a choice.
I was recently surprised when upgrading from Ubuntu 14 to 16 that it
replaced PHP 5 with 7 entirely. They were forced into choosing between the
two at a time when most developers will have to maintain both versions for
several more years for different projects.
And what do you mean --program-suffix is broken? What do you get and expect
to get? With or without my changes it seems work as intended.
2016-09-02 18:28 GMT+03:00 Levi Morrison <levim@php.net>:
> The issue is that you are writing to the same prefix. Just write them
> to different prefixes and reference them separately. This is not a
> unique-to-php situation. At work we maintain many different
> simultaneous versions of Python, for example.
>
> With that said it looks like the program suffixes are broken. If
> --program-suffix=7 is set then I'd expect php7, phpize7 (or php7ize,
> don't really care), etc.
>