packages when they switched to use bundled files in php-5.2.9.
Now we don't need this workaround any more and code itself already
no operation.
No functional change.
components are now built into PHP rather than maintained separately in
PECL. The old PECL versions are unmaintained and haven't been altered
for 3 years. This is confusing as the package versions report themselves
to be 5.2.9.1.0.2, etc. but they are in fact based on the 5.1.x code-base.
Therefore, we need to switch to building the PDO modules like any other
PHP module.
A side-effect of this is that the PECL version number will get stripped
off the end meaning that the new version numbers are just 5.2.9 instead
of 5.2.9.1.0.2 (for example). Unfortunately, 5.2.9 is considered to be
older than 5.2.9.1.0.2 meaning that it will appear as though a downgrade
has taken place. Therefore, while we are still using PHP 5.2.9, add .99 on
the end (i.e. 5.2.9.99) so that the package appears newer. When PHP 5.2.10
is released this can be removed (the module.mk file explicitly cgecks for
5.2.9 before adding the .99 suffix so that it will not alter 5.2.10 if the
hack is forgotten. However, for the record, when 5.2.10 is released,
php-pdo/module.mk can be removed along with the references to it in each
php-pdo*/Makefile
all PEAR packages to php?-pear-* and all Apache packages to ap13-* or
ap2-* respectively. Add new variables to simplify the Makefile
handling. Add CONFLICTS on the old names. Reset revisions of bumped
packages. ap-php will now depend on the default Apache and PHP version.
All programs using it have an implicit option of the Apache version
as well.
OK from jlam@ and adrianp@.
