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/009535.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009535.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-November/009535.html | 167 |
1 files changed, 167 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009535.html b/zarb-ml/mageia-dev/2011-November/009535.html new file mode 100644 index 000000000..dce6b8fd4 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009535.html @@ -0,0 +1,167 @@ +<!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=%3C4EC1A66E.2040406%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009534.html"> + <LINK REL="Next" HREF="009536.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] HEADSUP: mariadb available for testing</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20HEADSUP%3A%20mariadb%20available%20for%20testing&In-Reply-To=%3C4EC1A66E.2040406%40laposte.net%3E" + TITLE="[Mageia-dev] HEADSUP: mariadb available for testing">andre999mga at laposte.net + </A><BR> + <I>Tue Nov 15 00:38:22 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009534.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI>Next message: <A HREF="009536.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9535">[ date ]</a> + <a href="thread.html#9535">[ thread ]</a> + <a href="subject.html#9535">[ subject ]</a> + <a href="author.html#9535">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Maarten Vanraes a écrit : +><i> Hi all, +</I>><i> +</I>><i> mariadb-5.5.15-0.mga2 should be hitting the mirrors soon (at cauldron +</I>><i> core/updates_testing). It's purpose is to be an alternative to mysql. for that +</I>><i> reason, mariadb packages provide also the similar mysql targets. +</I>><i> +</I>><i> mariadb is intended to be a drop-in replacement for mysql, it goes so far to +</I>><i> actually have the same files and ABI's as mysql. after looking at their forking +</I>><i> process (it's not actually a full fork, they start from mysql and then patch), +</I>><i> i've seen that it's actually very good for a drop-in replacement. There are a +</I>><i> few differences ( <A HREF="http://kb.askmonty.org/en/mariadb-versus-mysql-compatibility">http://kb.askmonty.org/en/mariadb-versus-mysql-compatibility</A> +</I>><i> ) but they are minor. I've done a few minor tests with amarok, akonadi, drupal +</I>><i> and phpmyadmin (and of course mysql client). +</I>><i> +</I>><i> NOTE: mariadb provides actually most storage engines mysql provides as well, +</I>><i> but also the original and unpatched MyISAM and InnoDB engines from mysql. On +</I>><i> top of that, it has some extra storage engines. XtraDB, which is the drop-in +</I>><i> replacement storage engine for Innodb, is essentially an innodb with extra +</I>><i> patches from various sources, like google, facebook, etc... ( see +</I>><i> <A HREF="http://kb.askmonty.org/en/mariadb-versus-mysql-features">http://kb.askmonty.org/en/mariadb-versus-mysql-features</A> ) +</I>><i> +</I>><i> I've chosen to use mkrel 0 atm, because it's not a released version yet, I've +</I>><i> talked extensively to mariadb developers, and they mentioned that they did 5.3 +</I>><i> and 5.5 in parallel, so that 5.5 should be released as beta pretty soon. When +</I>><i> i talked about our release schedule, they did mention that mariadb-5.5 should +</I>><i> be final before februari. +</I>><i> +</I>><i> My plan is as follows: +</I>><i> 1. provide testing package [DONE] +</I>><i> 2. clean up spec file from mysql and file some patches upstream [DONE] +</I>><i> 3. provide newer testing package when it's released as a alpha/beta +</I>><i> 4. if testing is satisfactory (not breaking buildsystem or mysql) submit to +</I>><i> core/release and get more testing. +</I>><i> 5. if final 5.5 release is on time, have mariadb into mageia2 +</I>><i> +</I>><i> now there, we have a few options: +</I>><i> +</I>><i> considering that mariadb is essentially mysql + extra features, if we ship +</I>><i> both mysql and mariadb, we should ensure that normal users don't go from +</I>><i> mariadb to mysql. (if a storage engine would be used that's NOT in mysql, +</I>><i> suddenly a few databases might not work, even though the data is still there.) +</I>><i> +</I>><i> A. provide both but with vendor preference +</I>><i> making sure one of them both is preferred should be ok, since they conflict +</I>><i> anyway, if a user installs the non-preferred one, she knows what she's doing. +</I>><i> ( I think a note could be added here for warning purposes ) +</I>><i> +</I>><i> B. only use mariadb anymore +</I>><i> => That's the easiest and safest option... +</I>><i> _IF_ mariadb works well. (which i'm sure we'll see in our testing) +</I>><i> (IMHO, if it worked for libreoffice, i don't see why not for mariadb) +</I>><i> +</I>><i> +</I>><i> any opinions? testings? problems? +</I>><i> +</I>><i> +</I>I think it is a great idea, from all I've read. +I've already been thinking of installing it in place of mysql. + +As for the options, I'm inclined to prefer a choice (option A), since +some users could have problems with either, given that there are some +(minor) incompatibilities. +But if we have only one, at least those preferring the other could +always go upstream. + +As for what was done with Libreoffice/Openoffice, the obsolete forced me +to install upstream versions to have both installed. They have no file +conflict. +One can even have installed (but not run at the same time) different +versions of upstream Libreoffice at the same time. (They recommend +doing that for testing.) + +-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009534.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI>Next message: <A HREF="009536.html">[Mageia-dev] HEADSUP: mariadb available for testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9535">[ date ]</a> + <a href="thread.html#9535">[ thread ]</a> + <a href="subject.html#9535">[ subject ]</a> + <a href="author.html#9535">[ 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> |