diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010040.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010040.html | 139 |
1 files changed, 139 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010040.html b/zarb-ml/mageia-dev/2011-December/010040.html new file mode 100644 index 000000000..ab5c7a3fa --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010040.html @@ -0,0 +1,139 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Replacing mysql with mariadb + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Replacing%20mysql%20with%20mariadb&In-Reply-To=%3C201112010905.00756.alien%40rmail.be%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010226.html"> + <LINK REL="Next" HREF="010042.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Replacing mysql with mariadb</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Replacing%20mysql%20with%20mariadb&In-Reply-To=%3C201112010905.00756.alien%40rmail.be%3E" + TITLE="[Mageia-dev] Replacing mysql with mariadb">alien at rmail.be + </A><BR> + <I>Thu Dec 1 09:05:00 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010226.html">[Mageia-dev] Unable to boot into kernel-3.1.3 +</A></li> + <LI>Next message: <A HREF="010042.html">[Mageia-dev] Replacing mysql with mariadb +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10040">[ date ]</a> + <a href="thread.html#10040">[ thread ]</a> + <a href="subject.html#10040">[ subject ]</a> + <a href="author.html#10040">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + +in order to get more testing (mariadb is in core/updates_testing), i've +decided to submit to cauldron core/release, +however there lies a problem: + +Since everything is almost exact with mysql, same files and such, there are +some library conflicts which would present always a choice if we want both +mysql and mariadb (in particular libmysqlclient.so.X). Since we also want this +really used at build/link time one of both versions should be used. + +considering that mariadb mysql client works perfectly for both mysql and +mariadb. and that mysql mysql-client may not work perfectly for local servers +due to the my.cnf file being used for both client and server (mysql client is +supported for remote mariadb servers), I'd like to use the mariadb client +packages. + +The way I see it, there are 2 possibilities: +A. I remove the mysql-client, libmysqlclient, mysql-common and assorted +packages from mysql, and provide them with mariadb, since libmysqlclient is +drop-in replacable (same library ABI and such), there is not 100% requirement +of rebuilding all libmysqlclient dependant programs. + +advantages: + - both mariadb and mysql servers are present, people can choose +disadvantages: + - more QA + - more work for me + +B. We drop mysql completely and submit mariadb + +advantages: + - less work for me + - less work for QA +disadvantages: + - mysql is completely gone. + +I already posted this on the mariadb testing thread, but got little response, +So i plan to go with B really. because that'll give the best testing and if +mariadb isn't good enough, we can still modify mariadb and resubmit mysql. B +will have the best upgrade test (like for mga1 --> mga2) + +For more information regarding this, please read completely the mariadb +testing thread: +<A HREF="http://www.mail-archive.com/mageia-dev@mageia.org/msg09282.html">http://www.mail-archive.com/mageia-dev@mageia.org/msg09282.html</A> + +Some more bordering information: + - mariadb has XtraDB, which is essentially a patched InnoDB (it also supplies +an exact vanilla InnoDB as a plugin) + - mariadb still has myISAM support + - mariadb has as a default storage engine Aria (which can be used either as +transactional and as non-transactional) + - the files are exactly the same as mysql, it's still mysqld, mysql for client +so upgrading issues should be minimal, but still tested, of course. + +so please, test mariadb, build stuff against lib64mariadbclient18 +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010226.html">[Mageia-dev] Unable to boot into kernel-3.1.3 +</A></li> + <LI>Next message: <A HREF="010042.html">[Mageia-dev] Replacing mysql with mariadb +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10040">[ date ]</a> + <a href="thread.html#10040">[ thread ]</a> + <a href="subject.html#10040">[ subject ]</a> + <a href="author.html#10040">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |