summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20111115/35e00be6/attachment.html
blob: 0fbc1e28effa849211132b8df5c793da8907d6ae (plain)
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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>On 11/11/2011 10:17, Maarten Vanraes wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<pre>...
A. provide both but with vendor preference
making sure one of them both is preferred should be ok, since they conflict 
anyway, if a user installs the non-preferred one, she knows what she's doing.
( I think a note could be added here for warning purposes )

B. only use mariadb anymore
=&gt; That's the easiest and safest option...
_IF_ mariadb works well. (which i'm sure we'll see in our testing)
(IMHO, if it worked for libreoffice, i don't see why not for mariadb)


any opinions? testings? problems?
</pre>
</blockquote>
<p>I'm all for either of these. Especially B) if we can test it well enough.</p>
<p>I rebuilt the package on mga1 without issues. Tests fine as well.</p>
<p>Does anyone have any idea if the PBXT (Primebase) Storage Engine will be kept in MariaDB 5.5 (as it is in 5.1, 5.2, 5.3)?</p>
<div>
<pre>-- 
Sam Bailey

Cyprix Enterprises
Web: cyprix.com.au
Em: cyprix@cyprix.com.au
Mb: 0425 796 308</pre>
</div>
</body></html>