#3092 Change: MariaDB & MySQL repackaging
Closed: Accepted 6 months ago by zbyszek. Opened 6 months ago by amoloney.

A bigger set of smaller changes which I want to extend visibility for:

  • Drop builds for i686 architecture Note: no longer intended to be completed in F40 timeframe
  • Rename package 'community-mysql' to 'mysql' and Stop providing 'mysql' symbols by package 'mariadb'
  • Drop cross-installation functionality
  • Switch to the versioned layout of MariaDB and MySQL packages
  • Introduce MariaDB 10.11 and MySQL 8.1
  • Change the default MariaDB version in Fedora from 10.5 to 10.11

  • Change proposal

  • devel-announce post
  • Discussion
  • Owners: @mschorm

Owners, do not implement this work until the FESCo vote has explicitly ended.
The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed.
See the FESCo ticket policy and the Changes policy for more information.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the devel list thread linked above.


+1 in general

As @zbyszek mentioned in the Discussion ticket, I think the python-like approach to multi-versioning would be good for them to consider. (Node.js took a similar approach in https://www.fedoraproject.org/wiki/Changes/NodejsRepackaging

+1 (and I agree with @sgallagh's comment too).

+1 And I agree with everyone else. I think you'll have a much easier time doing what python does rather than adding a metapackage.

Acknowledged.
I'll give it a significant research before an actual implementation.

Metadata Update from @ngompa:
- Issue tagged with: self contained change

6 months ago

Is this one also ok to be marked as Approved with six +1 votes?

Thanks!

The statutory 7 days of voting passed after the last FESCo meeting, so it wasn't handled then. But enough time has passed now.

APPROVED (+6, 0, 0)

Metadata Update from @zbyszek:
- Issue tagged with: pending announcement

6 months ago

Metadata Update from @zbyszek:
- Issue untagged with: pending announcement
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

6 months ago

Login to comment on this ticket.

Metadata