diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-November/009923.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009923.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-November/009923.html | 111 |
1 files changed, 111 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009923.html b/zarb-ml/mageia-dev/2011-November/009923.html new file mode 100644 index 000000000..3824818a4 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009923.html @@ -0,0 +1,111 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] HEADSUP: mariadb available for testing + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20HEADSUP%3A%20mariadb%20available%20for%20testing&In-Reply-To=%3C201111290021.04769.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="009624.html"> + <LINK REL="Next" HREF="009926.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] HEADSUP: mariadb available for testing</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20HEADSUP%3A%20mariadb%20available%20for%20testing&In-Reply-To=%3C201111290021.04769.alien%40rmail.be%3E" + TITLE="[Mageia-dev] HEADSUP: mariadb available for testing">alien at rmail.be + </A><BR> + <I>Tue Nov 29 00:21:04 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009624.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI>Next message: <A HREF="009926.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9923">[ date ]</a> + <a href="thread.html#9923">[ thread ]</a> + <a href="subject.html#9923">[ subject ]</a> + <a href="author.html#9923">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + +in order to get more 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. + +If I get to choose, i'd know which one i would choose, but I'd like some +feedback on this point. + +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 , and give +opinion to which option to choose: A/B . +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009624.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI>Next message: <A HREF="009926.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9923">[ date ]</a> + <a href="thread.html#9923">[ thread ]</a> + <a href="subject.html#9923">[ subject ]</a> + <a href="author.html#9923">[ 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> |