[pkg-php-pear] Incoming changes in PHP packaging

Mathieu Parent math.parent at gmail.com
Sun Jul 12 14:13:36 UTC 2015

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)?

> 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 versions?

> 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.



More information about the pkg-php-pear mailing list