Soory, but seems a bad idea

With RHEL-7
php-mysql OR php-mysqlnd provides mysql, mysqli and pdo_mysql, so 3 extensions

With RHEL-8
php-mysqlnd provides mysqli and pdo_mysql, so only 2 extensions

The "mysql" extension doesn't exists anymore

We have a rule to provides php-foo for each provided extension
As we don'"t provide "mysql" extension, it doesn't make sense to add this provides


More, we have a packaging rule to require all used extensions (Fedora / EPEL)
So if a app really requires "mysql" extension (so php-mysql), it won't be usable with PHP 7+, so must not be installable

Would a meta package be acceptable? .. I'm thinking a lot of people will wonder where it went

@Remi,

Thank you for the feedback.  So, are these incompatible?  Thinking about the user experience, whenever possible it is best if this types of changes can be auto migrated limiting the friction for users to move to a new release.  We have many initiatives underway to improve the user experience and reduce this type of technical debt that we force on users.

Does this require code changes in user php code in how they initialize and use the ND version?  If so, that obviously makes this much harder.  What is the scope and impact outside of the rpm packaging?

If a user manually installs this ND version, must they also make code or config changes elsewhere?


If this is limited to installing the proper package, I propose we do what we can to automate this.

If installing the ND version of the package requires code changes, we need to ensure this is documented and in the release notes that the old driver has been deprecated and dropped from RHEL 8 and guidance on how the user must transition.

This will be *significant* for the in-place upgrades as it potentially creates significant friction for a user to move from RHEL 7->8.

(In reply to Terry Bowling from comment #3)
> Does this require code changes in user php code in how they initialize and
> use the ND version?  If so, that obviously makes this much harder.  What is
> the scope and impact outside of the rpm packaging?

Yes, extensions have different API
mysql_* functions http://php.net/mysqli
mysqli_* functions http://php.net/manual/en/book.mysql.php

> If a user manually installs this ND version, must they also make code or
> config changes elsewhere?

So, indeed, old code using mysql extension need to be fully rewritten.

AFAIK, most applications have switch to mysqli or pdo_mysql long time ago.

> If this is limited to installing the proper package, I propose we do what we
> can to automate this.
> 
> If installing the ND version of the package requires code changes, we need
> to ensure this is documented and in the release notes that the old driver
> has been deprecated and dropped from RHEL 8 and guidance on how the user
> must transition.

This have rather been dropped from PHP 7
and was deprecated for years...