Bug 753543

Summary:	Packaging MariaDB in Fedora
Product:	[Fedora] Fedora	Reporter:	Colin Charles <byte>
Component:	distribution	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DEFERRED	QA Contact:	Bill Nottingham <notting>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	byte, dennis, rvokal, tcallawa
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-13 19:09:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Colin Charles 2011-11-13 09:47:23 UTC

Description of problem: MariaDB is an opensource branch of MySQL, with enhanced features, that aims to be backward compatible with MySQL. More information at http://www.mariadb.org/

Version-Release number of selected component (if applicable): 5.2 is currently the stable release. 5.3 is currently in beta, and includes solutions like HandlerSocket, a tonne of optimiser features and more. Its based on MySQL 5.1.

Additional info: MariaDB is a drop-in replacement to MySQL. In an ideal environment it should Obsolete: mysql. However this seems to be against Fedora packaging guidelines. Do we investigate using Alternatives?

Comment 1 Tom "spot" Callaway 2011-11-14 14:36:43 UTC

As I mentioned to you when we spoke last Colin, I see no reason why MariaDB could not be packaged using alternatives. Conflicting or Obsoleting MySQL would not be permitted.

Comment 2 Bill Nottingham 2011-11-15 04:33:17 UTC

... is this intended to be a package review bug? Or a general RFE?

Comment 3 Bill Nottingham 2011-12-13 19:09:25 UTC

Closing this - if someone wants MariaDB, they can open a package review.