|| ||Honza Horak <hhorak-AT-redhat.com> |
|| ||Development discussions related to Fedora <devel-AT-lists.fedoraproject.org> |
|| ||Re: Proposed F19 Feature: Replace MySQL with MariaDB |
|| ||Tue, 29 Jan 2013 16:30:56 +0100|
|| ||Article, Thread
On 01/26/2013 10:33 PM, "Jóhann B. Guðmundsson" wrote:
> On 01/26/2013 08:42 PM, Pierre-Yves Chibon wrote:
>> On Sat, 2013-01-26 at 21:34 +0100, Reindl Harald wrote:
>>> Am 26.01.2013 21:24, schrieb Pierre-Yves Chibon:
>>>>> but keep in mind that Fedora is the base for RHEL
>>>>> applications may be certified for mysql
>>>> And that is Fedora's problem how?
>>> and THAT is the problem with many pieces of fedora-development
>>> the last few years - what do we care for the real world usage,
>>> we are only a design study......
>> I agree, we care for real world usage of Fedora, not XYZ.
> Yup rhel != Fedora
> The third party support can be distribution agnostic like for example 
> Running on Fedora does not break support there however using mariadb will.
> If the current maintainers orphan mysql anyone can pick it up including
> Oracle employees and continue it's maintenance within the distribution.
> Any beef, competition or what not between Red Hat and Oracle ( or anyone
> else for that matter ) is between Red Hat and Oracle not Fedora and I
> cant imagine FESCO/Board standing in the way of Oracle wanting to
> packaging and maintain anything in the distribution unless it breaks
> some legal jargon just like everyone else.
Going through the thread I currently see two reasons to keep packaging
mysql after switching to mariadb:
Firstly, some admins may be bound to mysql because of the certification
or similar reason, but it probably won't be a technical reason. It'd be
nice if admins work with providers in such cases and push them to add
mariadb into set of "supported" options. I believe there won't be
technical barrier to do so, so everyone could benefit from that.
Second, if mariadb differs more in the future and stops to be "drop-in"
replacement, then we'll need an alternative for applications, where
mariadb won't be suitable enough. Nevertheless, this is not a current
issue right now.
In both cases we'll probably need some time to evaluate how the things
with mariadb goes, so I'd suggest to wait, observe, test and after some
time to re-open the discussion and make a decision about dropping mysql.
When we're talking about testing, there is a mariadb package built in
We're not using obsoletes for now, so in order to install the builds you
can do the following (after the packages will by synced into rawhide repo):
# yum shell --enablerepo=rawhide
Loaded plugins: langpacks, presto, refresh-packagekit
> remove mysql mysql-libs ...
> install mariadb mariadb-libs ...
Sub-package names of mariadb correspond with sub-packages of mysql.
devel mailing list
to post comments)