[php-maint] [Pkg-php-pecl] [pkg-php-pear] Incoming changes in PHP packaging
ondrej at sury.org
Mon Jul 13 11:20:04 UTC 2015
On Sun, Jul 12, 2015, at 16:13, Mathieu Parent wrote:
> 2015-07-09 16:00 GMT+02:00 Ondřej Surý <ondrej at sury.org>:
> > Hi all,
> All this is great. I welcome those changes.
> Does this mean that we plan to support several versions at once (in
> stretch and later)?
Yes, however the exact versions will have to be negotiated with release
and security teams.
But we will have to support at least one of 5.x and 7.x versions in
stretch. The rest can be supported by an outside repository.
> > The next steps will be crucial and it will require a lot of work (but
> > there's no easy way how to do that). We want to create a system similar
> > to python-<module> or ruby-<module>
> > 1. The binary modules will have to be renamed from php5-<module> to
> > php-<module>
> It means modules from src:phpX.Y and also any PECL package...
> > 2. Each binary package will include versions of the module built for all
> > available PHP versions
> But what about backports? Should we use something like dkms for extra
There will be src:php-defaults providing something like php-all-dev and
something will know about all supported versions in that release.
See https://wiki.debian.org/Python/TransitionToDHPython2 for
I am also thinking about:
so you can specify PHP Versions (or ZEND_API?) your package supports.
> > 3. src:phpX.Y will stop building all modules (except the compiled-in)
> > 4. src:php-modules (probably with same source as phpLATEST, but each
> > module will be individually built for every available PHP version)
> > 5. (optional)I think we should have a system in place that would allow
> > us to have sources for each PHP version. I am thinking about modules
> > that couldn't be compiled for older PHP versions, but we still want to
> > provide. The second option would be to patch the sources to detect the
> > PHP version at compile time.
> > As for PEAR:
> > As previously discussed - I have dropped building php-pear from
> > src:php7.0, so it will have to be packaged individually. Any volunteers
> > (or at least people who care)?
> pkg-php-tools currently needs PEAR (only for the debhelper
> buildsystem, i.e --buildsystem=phppear), at least I care ... but I
> need some free time.
> The plan will need development on the pkg-php-tools side to support
> several php-config.
I think this is the place where Murukesh should look next after we
finish the changes to the versioned PHP packaging.
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
More information about the pkg-php-maint