On Wed, Jan 28, 2015 at 8:10 AM, Jan Ehrhardt <php...@ehrhardt.nl> wrote: > Sebastian Bergmann in php.internals (Tue, 27 Jan 2015 21:36:49 +0100): >>Am 27.01.2015 um 21:13 schrieb Pierre Joye: >>> However there is one thing we do need to care, and this is 3rd party >>> extensions. This is all I care about and why I initiated pickle. >> >> It just that I am not convinced that the problem you are trying to solve >> with a tool such as pickle exists. From my experience, people either >> build everything manually from source (because they work on the source) >> or they install binaries packaged by a vendor using the appropriate >> package manager. > > The problem is a real one. One example: for Windows PECL extensions are > buolt at http://windows.php.net/downloads/pecl/
they are available on http://pecl.php.net, only snapshots are there only. > The current trend makes it virtually impossible to add PHP7 to these > builds, because for instance you have to checkout 'phpng' branches for > propro, raphf and pecl_http and the 'phpseven' branch for imagick. At > the moment that these branches are merged into master and separate > branches for PHP5 are created, the PHP5 builds will be broken. > > If you aren't involved in developing the sources of an extension it > becomes a trial-and-error game to see if the extension builds for PHP7. This is not specific to windows. Having discussed that with many distros, developers, ISPs etc. this is actually a big problem. The biggest being the totally meaningless of a branch from a semver point of view. What to do with a package version where there is no difference in the public API for 5 and 7? 2.x for 7 and 1.x for 5? What's next? 3. for 7 and 4.x for 8? this is an endless pain. That's why I would rather propose a single branch for any php supported php version, as we always have done. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
