diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-August/017898.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-August/017898.html | 140 |
1 files changed, 140 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-August/017898.html b/zarb-ml/mageia-dev/2012-August/017898.html new file mode 100644 index 000000000..fe0636bf6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017898.html @@ -0,0 +1,140 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Library%20policy%20query%3A%20What%20do%20we%20do%20when%20SONAME%0A%20includes%20both%20major%20and%20minor%3F%20%28Re%3A%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%20kdelibs4-4.9.0-2.mga3%29&In-Reply-To=%3C501A45BF.5060103%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="017897.html"> + <LINK REL="Next" HREF="017899.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Library%20policy%20query%3A%20What%20do%20we%20do%20when%20SONAME%0A%20includes%20both%20major%20and%20minor%3F%20%28Re%3A%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%20kdelibs4-4.9.0-2.mga3%29&In-Reply-To=%3C501A45BF.5060103%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)">mageia at colin.guthr.ie + </A><BR> + <I>Thu Aug 2 11:17:51 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="017897.html">[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) +</A></li> + <LI>Next message: <A HREF="017899.html">[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17898">[ date ]</a> + <a href="thread.html#17898">[ thread ]</a> + <a href="subject.html#17898">[ subject ]</a> + <a href="author.html#17898">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Balcaen John at 02/08/12 10:01 did gyre and gimble: +><i> Le jeudi 2 août 2012 09:28:28 Colin Guthrie a écrit : +</I>>><i> 'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and +</I>>><i> +</I>>><i> gimble: +</I>>>><i> On Wed, 1 Aug 2012, Colin Guthrie wrote: +</I>>>>><i> I have to agree here that something is "funny" in the libattica package +</I>>>>><i> which ultimately helped to contribute to this issue. +</I>>>>><i> +</I>>>>><i> e.g. on my system before update (tho' with similar results after): +</I>>>>><i> +</I>>>>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">colin at jimmy</A> ~]$ rpm -q --provides lib64attica0 +</I>>>>><i> libattica.so.0.3()(64bit) +</I>>>>><i> lib64attica0 = 0.3.0-1.mga2 +</I>>>>><i> lib64attica0(x86-64) = 0.3.0-1.mga2 +</I>>>>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">colin at jimmy</A> ~]$ rpm -ql lib64attica0 +</I>>>>><i> /usr/lib64/libattica.so.0.3 +</I>>>>><i> /usr/lib64/libattica.so.0.3.0 +</I>>>>><i> +</I>>>>><i> So I can see how this mistake was made and TBH I could have made the +</I>>>>><i> same mistake myself (with the caveat that I likely would not have bumped +</I>>>>><i> the version of someone else's package with out confirming first and that +</I>>>>><i> it should have been obvious from testing and installing the build) +</I>>>>><i> +</I>>>>><i> But either way this seems like an issue to fix properly (possibly with +</I>>>>><i> an upstream fix or some modification to the library policy when the +</I>>>>><i> minor version is "presented" like this). +</I>>>><i> +</I>>>><i> Good catch! Of course it's never the library policy that's wrong. The +</I>>>><i> library major version is apparently 0.4 so the correct package name is +</I>>>><i> +</I>>>><i> lib64attica0.3 for the previous one +</I>>>><i> lib64attica0.4 for the current one +</I>>>><i> +</I>>>><i> ... in the specfile: %define attica_major 0.4 +</I>>>><i> +</I>>>><i> Can the maintainer of this package please fix this? +</I>>>><i> +</I>>>><i> To find the version to use, look up the 'soname' of the library. I use: +</I>>>><i> readelf -a /usr/lib64/libattica.so.0.4|grep SONAME +</I>>>><i> +</I>>>><i> => +</I>>>><i> ... Library soname: [libattica.so.0.4] +</I>>>><i> +</I>>>><i> What follows ".so." is the major version of the library. +</I>>><i> +</I>>><i> Is that really the correct definition of what a "major" version is? +</I>>><i> +</I>>><i> I always thought the major was just the first number. +</I>>><i> +</I>>><i> The library policy certainly doesn't mention "double digit majors" or +</I>>><i> similar. +</I>>><i> +</I>>><i> Is this something upstream is doing deliberately or is it just an oversight? +</I>><i> <A HREF="https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/CMakeLists.txt">https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/CMakeLists.txt</A> +</I> +Actually it's this file/line: + +<A HREF="https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/lib/CMakeLists.txt#L120">https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/lib/CMakeLists.txt#L120</A> + +So it's seems like this was done deliberately due to a ABI breakage a +while ago: + +<A HREF="https://projects.kde.org/projects/kdesupport/attica/repository/revisions/ac2270b1f9c445fd39e48051b99d35d9b9693a34">https://projects.kde.org/projects/kdesupport/attica/repository/revisions/ac2270b1f9c445fd39e48051b99d35d9b9693a34</A> + +Now, this is an interesting point (regarding our lib policy) bumping the +major for an API change and the minor for an ABI change seems kinda +sensible to me. So how should we deal with that in our policy? Just use +0.4 as the "major" value here as Christiaan suggested? + +Col + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="017897.html">[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) +</A></li> + <LI>Next message: <A HREF="017899.html">[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17898">[ date ]</a> + <a href="thread.html#17898">[ thread ]</a> + <a href="subject.html#17898">[ subject ]</a> + <a href="author.html#17898">[ 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> |