mysql: replace mysql with mariadb 10.0
RFC 1/1 mysql: replace mysql with mariadb 10.0
Quoted 6 lines
Quoted 1 line
/This patch represents my attempt to replace the aging mysql 5.1 that is />/currently shipped with Buildroot. I am replacing mysql altogether with
mariadb />/version 10.0. I have been able to test this with both an arm and a
x86_64/>/build. I have not tested it with systemd. This patch is based on the work done />/by Sylvain Raybaud. /
Would it be better to just add MariaDB rather than replace MySQL, there's reasons to use one over the other.
While a virtual package may be helpful if in the future someone would like to add another MySQL implementation.
I do have concerns about the existing mysql package, given that:
- the MySQL branch used has been EOL since 2013
- there has been an number of CVE issues since:
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=oracle+mysql
(and cve-2016-6662 not yet in the list)
- it listens to all interfaces by default
How responsible is it to keep packages in such state around, when there do are alternatives?
Yours sincerely,
Floris Bos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160915/5ca5ee8f/attachment.html>
RFC 1/1 mysql: replace mysql with mariadb 10.0
Quoted 9 lines · Floris Bos
Quoted 3 lines
Quoted 1 line
/This patch represents my attempt to replace the aging mysql 5.1 that is />/currently shipped with Buildroot. I am replacing mysql altogether with mariadb />/version 10.0. I have been able to test this with both an arm and a
x86_64/>/build. I have not tested it with systemd. This patch is based on the work done />/by Sylvain Raybaud. /Would it be better to just add MariaDB rather than replace MySQL, there's reasons to use one over the other.
While a virtual package may be helpful if in the future someone would like to add another MySQL implementation.
I do have concerns about the existing mysql package, given that:
Quoted 8 lines
- the MySQL branch used has been EOL since 2013
- there has been an number of CVE issues since:
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=oracle+mysql
(and cve-2016-6662 not yet in the list)
- it listens to all interfaces by defaultHow 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.
Regards,
Arnout
Quoted 11 lines
Yours sincerely,
Floris Bos
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
RFC 1/1 mysql: replace mysql with mariadb 10.0
Hello,
Quoted 8 lines · Arnout Vandecappelle
Quoted 2 lines
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com