Some people are making "compatibility headers" consisting of a big number of macros. It's inconvenient for extensions widely using Zend API. It's not very beautiful solution as well.
I got an idea: config.m4 can take care by means of a couple of directories: php7 and pre-php7. But the package size will be nearly doubled. What do you think about it? Perhaps, somebody has invented an elegant solution already? On Sun, 15 Nov 2015 15:30:12 +0500 Ruslan Osmanov <[email protected]> wrote: > Hi, > > how do I package a PHP7 extension? > > Say, we have an extension with PHP5+ support with version 1.0.0. Since > PHP7 internal API is not backwards compatible, we're re-writing the > code in a branch. We bump its version to 2.0.0. Now what happens, if > we upload the PHP7 version to PECL? A PHP6 user will be unable to > build it. He won't be able to upgrade the extension either. > > The only thing I can do is to specify minimum PHP version in > package.xml. Is it enough? > -- Ruslan Osmanov
signature.asc
Description: PGP signature
