diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010579.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010579.html | 170 |
1 files changed, 170 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010579.html b/zarb-ml/mageia-dev/2011-December/010579.html new file mode 100644 index 000000000..7d69eb06b --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010579.html @@ -0,0 +1,170 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] mariadb + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mariadb&In-Reply-To=%3C201112171710.29331.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="010594.html"> + <LINK REL="Next" HREF="010606.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] mariadb</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mariadb&In-Reply-To=%3C201112171710.29331.alien%40rmail.be%3E" + TITLE="[Mageia-dev] mariadb">alien at rmail.be + </A><BR> + <I>Sat Dec 17 17:10:29 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010594.html">[Mageia-dev] mariadb +</A></li> + <LI>Next message: <A HREF="010606.html">[Mageia-dev] mariadb +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10579">[ date ]</a> + <a href="thread.html#10579">[ thread ]</a> + <a href="subject.html#10579">[ subject ]</a> + <a href="author.html#10579">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 17 december 2011 14:23:54 schreef Funda Wang: +><i> 2011/12/17 Maarten Vanraes <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>>: +</I>><i> > ah, didn't see that one... i've put the mklibnames in variables and +</I>><i> > resubmitted. +</I>><i> > +</I>><i> > perhaps this can be documented somewhere(.spec file policy), or even +</I>><i> > better, fixed? +</I>><i> +</I>><i> %mklibname takes a lot of parameters, so: +</I>><i> +</I>><i> Requires: %mklibname mysql %{major} = %{version}-%{release} +</I>><i> +</I>><i> will let %mklibname think its parameters are: +</I>><i> %1: mysql +</I>><i> %2: %{major} +</I>><i> %3: = +</I>><i> %4: %{version}-%{release} +</I>><i> +</I>><i> After parsing, %mklibname only recognize the first three paramerters, +</I>><i> and put an underscore between %2 and %3. so it becomes: +</I>><i> +</I>><i> %{_lib}mysql%{major}_= +</I>><i> +</I>><i> And, %4(%{version}-%{release}) will be throw away. +</I> +right, i figured it out, after i saw it. thanks for the lengthy explanation. +Speaking with Anssi about this, he mentions that + +%{mklibname mysql %{major}} = %{version}-%{release} + +would have also solved the issue. + +><i> > PS: I provided the exact provides as mysql, just to be sure that there is +</I>><i> > no mageia (or otherwise 3rd party package) could be having troubles +</I>><i> > finding the correct packages. +</I>><i> +</I>><i> As mariadb is a binary replacement for mysql, why not just named the +</I>><i> libs as %{_lib}mysql18 and %{_lib}mysqld18, which is more accurate +</I>><i> than %{_lib}mariadb18. Almost all the packages are using binary +</I>><i> dependencies (libmysqlclient.so.18) rather than rpm name dependencies, +</I>><i> which is more nature than package name, and more reliable. +</I> +i understand, however the %mklibname macro is actually meant for this, and +will not change. + +furthermore, speaking with Anssi about this, + +><i> Personally, I don't think libmysqld18 (now it is named +</I>><i> libmariadb-embedded18) should have any relationship with libmysqld0. +</I>><i> They have different libmajor, which means all the packages depending +</I>><i> on libmysqld0 should be recompiled. So basically, they are different +</I>><i> libs actually. Adding symbolic link won't provide any help, either. +</I> +in respect to the embedded libraries, it's not actually, + +their upstream version was more or less copied from mysql and the developer +who implemented the cmake change in 5.5 branch for mysql, is the same person +who's now maintaining that 5.5 cmake branch. + +I mentioned that this library should be versioned, and that it's not at this +time, he agreed, and said that since it's ABI compatible with mysqlclient, +that he should not use 0 major, but the 18 major (same as mysqlclient) + +the code is still 100% exactly the same, it just went from unversioned in +upstream to versioned. + +since we had versioned manually mysqld to major 0, i provided the +compatibility symlinks for it. +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010594.html">[Mageia-dev] mariadb +</A></li> + <LI>Next message: <A HREF="010606.html">[Mageia-dev] mariadb +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10579">[ date ]</a> + <a href="thread.html#10579">[ thread ]</a> + <a href="subject.html#10579">[ subject ]</a> + <a href="author.html#10579">[ 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> |