MariaDB and MySQL Renaming
Summary
Rename community-mysql to mysql. Do not provide any mysql symbols by MariaDB packages any more.
Owner
- Name: Honza Horak
- Email: hhorak@redhat.com
Current status
- Targeted release: Fedora 37
- Last updated: 2023-10-06
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
When MariaDB was introduced to Fedora, it seemed like it eventually replaces MySQL and therefore the packages were designed so that mysql names were provided by MariaDB and MySQL was renamed to community-mysql. The both projects were drop-in replacements that time, so that design also helped smooth transition. Since then, a lot changed, MariaDB diverged from MySQL pretty lot, so it does not make sense to call it mysql (in RPM provides) any more. Also, the package name community-mysql are Fedora specific. Oracle upstream uses mysql-community, debian and RHEL use mysql names. To keep the naming convention more close to other Fedora-related clones, the proposal is to rename the MySQL packages to mysql-*.
Feedback
Feedback to be gathered.
Benefit to Fedora
This removes the friction about naming of the packages and moves Fedora closer to what is the naming outside. Users will get true MySQL when asking for mysql by dnf. Also, users will be able to write scripts and config files that work the same across the Fedora-related distros like RHEL and CentOS.
Scope
- Proposal owners:
- Remove mysql names in the MariaDB packages
- Follow the guidelines for renaming the package for community-mysql component
- ✔️ Prepare pull-requests for depended packages (see Other developers section) and help merging them
- Other developers:
- ✔️ Update build-requires that currently use obsoleted mysql-devel as a BuildRequire, but really should be built with mariadb-connector-c
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)