From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-December/010575.html | 131 +++++++++++++++++++++++++++ 1 file changed, 131 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010575.html (limited to 'zarb-ml/mageia-dev/2011-December/010575.html') diff --git a/zarb-ml/mageia-dev/2011-December/010575.html b/zarb-ml/mageia-dev/2011-December/010575.html new file mode 100644 index 000000000..85191f276 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010575.html @@ -0,0 +1,131 @@ + + + + [Mageia-dev] mariadb + + + + + + + + + +

[Mageia-dev] mariadb

+ Balcaen John + mikala at mageia.org +
+ Sat Dec 17 16:22:50 CET 2011 +

+
+ +
Le samedi 17 décembre 2011 17:14:52 Anssi Hannula a écrit :
+> On 17.12.2011 15:59, Oliver Burger wrote:
+> > Am Samstag, 17. Dezember 2011, 15:45:42 schrieb Anssi Hannula:
+> >> +1 for not naming it as libmariadb18 if it actually contains
+> >> libmysqlclient.so.18.
+> > 
+> > But mariadb is not mysql, it's a kind of fork of mysql.
+> > 
+> > We don't call libreoffice openoffice and we don't call Mageia Mandriva, do
+> > we?
+> Fair points.
+> 
+> IMHO library packages should still be primarily named after the library
+> they contain, regardless of project name.
+> 
+> But indeed we have no clear policy regarding that, making it kind of
+> maintainer decision.
+Well since we still don't know if we're going to follow mariadb path or mysql, 
+we should probably better stick to mariadb inside the library name.
+(Not to mention we don't know if mariadb is not going to change the library's 
+name from libmysql to libmariadb.)
+
+Regards,
+ 
+-- 
+Balcaen John
+Jabber-id: mikala at jabber.littleboboy.net
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1