1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
<!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=%3CCAL%2BdqvBrXBoTwnZZJLBVektRjjcw3nhGpc_jqN90SPOG5brXmg%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010040.html">
<LINK REL="Next" HREF="010070.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Replacing mysql with mariadb</H1>
<B>D.Morgan</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Replacing%20mysql%20with%20mariadb&In-Reply-To=%3CCAL%2BdqvBrXBoTwnZZJLBVektRjjcw3nhGpc_jqN90SPOG5brXmg%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Replacing mysql with mariadb">dmorganec at gmail.com
</A><BR>
<I>Thu Dec 1 09:42:13 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010040.html">[Mageia-dev] Replacing mysql with mariadb
</A></li>
<LI>Next message: <A HREF="010070.html">[Mageia-dev] Replacing mysql with mariadb
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10042">[ date ]</a>
<a href="thread.html#10042">[ thread ]</a>
<a href="subject.html#10042">[ subject ]</a>
<a href="author.html#10042">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Thu, Dec 1, 2011 at 9:05 AM, Maarten Vanraes <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote:
><i> Hi,
</I>><i>
</I>><i> in order to get more testing (mariadb is in core/updates_testing), i've
</I>><i> decided to submit to cauldron core/release,
</I>><i> however there lies a problem:
</I>><i>
</I>><i> Since everything is almost exact with mysql, same files and such, there are
</I>><i> some library conflicts which would present always a choice if we want both
</I>><i> mysql and mariadb (in particular libmysqlclient.so.X). Since we also want this
</I>><i> really used at build/link time one of both versions should be used.
</I>><i>
</I>><i> considering that mariadb mysql client works perfectly for both mysql and
</I>><i> mariadb. and that mysql mysql-client may not work perfectly for local servers
</I>><i> due to the my.cnf file being used for both client and server (mysql client is
</I>><i> supported for remote mariadb servers), I'd like to use the mariadb client
</I>><i> packages.
</I>><i>
</I>><i> The way I see it, there are 2 possibilities:
</I>><i> A. I remove the mysql-client, libmysqlclient, mysql-common and assorted
</I>><i> packages from mysql, and provide them with mariadb, since libmysqlclient is
</I>><i> drop-in replacable (same library ABI and such), there is not 100% requirement
</I>><i> of rebuilding all libmysqlclient dependant programs.
</I>><i>
</I>><i> advantages:
</I>><i>  - both mariadb and mysql servers are present, people can choose
</I>><i> disadvantages:
</I>><i>  - more QA
</I>><i>  - more work for me
</I>><i>
</I>><i> B. We drop mysql completely and submit mariadb
</I>><i>
</I>><i> advantages:
</I>><i>  - less work for me
</I>><i>  - less work for QA
</I>><i> disadvantages:
</I>><i>  - mysql is completely gone.
</I>><i>
</I>><i> I already posted this on the mariadb testing thread, but got little response,
</I>><i> So i plan to go with B really. because that'll give the best testing and if
</I>><i> mariadb isn't good enough, we can still modify mariadb and resubmit mysql. B
</I>><i> will have the best upgrade test (like for mga1 --> mga2)
</I>><i>
</I>><i> For more information regarding this, please read completely the mariadb
</I>><i> testing thread:
</I>><i> <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>
</I>><i>
</I>><i> Some more bordering information:
</I>><i>  - mariadb has XtraDB, which is essentially a patched InnoDB (it also supplies
</I>><i> an exact vanilla InnoDB as a plugin)
</I>><i>  - mariadb still has myISAM support
</I>><i>  - mariadb has as a default storage engine Aria (which can be used either as
</I>><i> transactional and as non-transactional)
</I>><i>  - the files are exactly the same as mysql, it's still mysqld, mysql for client
</I>><i> so upgrading issues should be minimal, but still tested, of course.
</I>><i>
</I>><i> so please, test mariadb, build stuff against lib64mariadbclient18
</I>
we have several critical stuffs working on mysql, can't we wait for
mga3 to work on this ?
We already broke a lot of stuffs in cauldron for now ( systemd is the
more important ). Mikala told that akonadi works with mysql so before
pushing in core/release i would appreciate you work on this to make
sure it builds/works with mariadb.
can you ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010040.html">[Mageia-dev] Replacing mysql with mariadb
</A></li>
<LI>Next message: <A HREF="010070.html">[Mageia-dev] Replacing mysql with mariadb
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10042">[ date ]</a>
<a href="thread.html#10042">[ thread ]</a>
<a href="subject.html#10042">[ subject ]</a>
<a href="author.html#10042">[ 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>
|
