mysql8: Update to 8.4.x; remove mysql81 and mysql82 ports and variants

[ryandesign (Ryan Carsten Schmidt)]

The mysql8 port does not track 8.x versions of MySQL; it tracks 8.0.x versions. (The mysql81 and mysql82 ports for the 8.1.x and 8.2.x versions already exist.) Can anything be done about that now (renaming the mysql8 port to mysql80) or will that cause too much disruption? For example, user's database files will be in a "mysql8" path on disk; simply changing all the paths and config settings to "mysql80" would disconnect the user's data from the server. Maybe compatibility symlinks can be used. For the data directory, leave it where it is in a "mysql8" path but add a "mysql80" symlink to it. For all the other paths and config settings, change them to "mysql80".

[ryandesign (Ryan Carsten Schmidt)]

Or perhaps not.

It looks like Oracle has decided to confuse how version numbers work starting with 8.0:

​https://dev.mysql.com/blog-archive/introducing-mysql-innovation-and-long-term-support-lts-versions/

As I now understand it, MySQL 8 is now an LTS release starting with version 8.4. Therefore it seems the mysql8 port should update to 8.4.x and the mysql81 and mysql82 ports should never have been created and should be replaced_by mysql8. mysql81 and mysql82 variants in other ports should be changed to requires mysql8.

[herbygillot (Herby Gillot)]

See: ​https://github.com/macports/macports-ports/pull/23958

[herbygillot (Herby Gillot)]

In 6562a93234ac1045080fc9726e61334b08548666/macports-ports (master):

mysql8: update to 8.4.0

• mysql82 and mysql81 are now replaced by mysql8

Fixes: #69934