From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [1/1,RFC] mysql: replace mysql with mariadb 10.0
Date: Sat, 17 Sep 2016 15:50:30 +0200 [thread overview]
Message-ID: <20160917155030.3eb602eb@free-electrons.com> (raw)
In-Reply-To: <0775fdeb-5056-73cd-4cf8-7d4edeb6d8a7@mind.be>
Hello,
On Thu, 15 Sep 2016 23:17:51 +0200, Arnout Vandecappelle wrote:
> > How responsible is it to keep packages in such state around, when there do are
> > alternatives?
>
> True. But it should be relatively easy to bump the existing mysql package. If
> it is completely replaced by mariadb, it won't be so easy anymore.
>
> We could mark mysql as deprecated pending the bump. That could motivate people
> to step up and fix it.
As Floris said, our mysql package is deprecated, so I'm all for
replacing it with an up-to-date mariadb package. If later on, someone
else really needs MySQL, we can re-add it, and add the necessary
virtual package to allow selecting between mysql and mariadb. But until
there's a decent mysql package available, I believe replacing it
completely with an up-to-date mariadb package is better.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-17 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 21:09 [Buildroot] [1/1,RFC] mysql: replace mysql with mariadb 10.0 Floris Bos
2016-09-15 21:17 ` Arnout Vandecappelle
2016-09-17 13:50 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-12 22:05 [Buildroot] [PATCH 1/1] [RFC] " Ryan Coe
2016-09-14 14:46 ` [Buildroot] [1/1,RFC] " Floris Bos
2016-09-14 18:44 ` Ryan Coe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160917155030.3eb602eb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox