summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006603.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006603.html')
-rw-r--r--zarb-ml/mageia-dev/2011-July/006603.html158
1 files changed, 158 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006603.html b/zarb-ml/mageia-dev/2011-July/006603.html
new file mode 100644
index 000000000..6a2a7bd7b
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-July/006603.html
@@ -0,0 +1,158 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Standardising the virtual Provides in -devel packages
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Standardising%20the%20virtual%20Provides%20in%20-devel%0A%09packages&In-Reply-To=%3CCAJmd%2BxrQJcRVzh7cG5eWVG%2B7PULv0TBPmxy_zx4r5OXox51xxg%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="006602.html">
+ <LINK REL="Next" HREF="006879.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Standardising the virtual Provides in -devel packages</H1>
+ <B>Ahmad Samir</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Standardising%20the%20virtual%20Provides%20in%20-devel%0A%09packages&In-Reply-To=%3CCAJmd%2BxrQJcRVzh7cG5eWVG%2B7PULv0TBPmxy_zx4r5OXox51xxg%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] Standardising the virtual Provides in -devel packages">ahmadsamir3891 at gmail.com
+ </A><BR>
+ <I>Wed Jul 13 12:41:22 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006602.html">[Mageia-dev] Standardising the virtual Provides in -devel packages
+</A></li>
+ <LI>Next message: <A HREF="006879.html">[Mageia-dev] Standardising the virtual Provides in -devel packages
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6603">[ date ]</a>
+ <a href="thread.html#6603">[ thread ]</a>
+ <a href="subject.html#6603">[ subject ]</a>
+ <a href="author.html#6603">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 13 July 2011 12:34, nicolas vigier &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">boklm at mars-attacks.org</A>&gt; wrote:
+&gt;<i> On Wed, 13 Jul 2011, Ahmad Samir wrote:
+</I>&gt;<i>
+</I>&gt;&gt;<i> On 10 July 2011 10:03, Ahmad Samir &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>&gt; wrote:
+</I>&gt;&gt;<i> &gt; On 8 July 2011 06:37, Ahmad Samir &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>&gt; wrote:
+</I>&gt;&gt;<i> &gt;&gt; Hello.
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; I've had a rather vague idea about standardising the virtual provides
+</I>&gt;&gt;<i> &gt;&gt; in the distro, there should be:
+</I>&gt;&gt;<i> &gt;&gt; Provides: %{name}-devel
+</I>&gt;&gt;<i> &gt;&gt; Provides: lib%{name}-devel
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; either both of them in _all_ packages, or one of them in _all_
+</I>&gt;&gt;<i> &gt;&gt; packages, so that we don't have to check urpmq --provides all the
+</I>&gt;&gt;<i> &gt;&gt; time. Personally, I am more inclined on having them both, so as not to
+</I>&gt;&gt;<i> &gt;&gt; break already working specs.
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; For example:
+</I>&gt;&gt;<i> &gt;&gt; $ urpmq --provides lib64gudev1.0-devel-166-5.mga1.x86_64
+</I>&gt;&gt;<i> &gt;&gt; libgudev-devel[== 166-5.mga1]
+</I>&gt;&gt;<i> &gt;&gt; pkgconfig(gudev-1.0)[== 166]
+</I>&gt;&gt;<i> &gt;&gt; devel(libgudev-1.0(64bit))
+</I>&gt;&gt;<i> &gt;&gt; lib64gudev1.0-devel[== 166-5.mga1]
+</I>&gt;&gt;<i> &gt;&gt; lib64gudev1.0-devel(x86-64)[== 166-5.mga1]
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; only libgudev-devel, so if I put BR gudev-devel in a spec it won't
+</I>&gt;&gt;<i> &gt;&gt; work, whereas I'd expect it to work since some other packages have
+</I>&gt;&gt;<i> &gt;&gt; such similar provides:
+</I>&gt;&gt;<i> &gt;&gt; $ urpmq --provides lib64dbus-1-devel
+</I>&gt;&gt;<i> &gt;&gt; libdbus-1-devel[== 1.4.1-3.mga1]
+</I>&gt;&gt;<i> &gt;&gt; libdbus-devel[== 1.4.1-3.mga1]
+</I>&gt;&gt;<i> &gt;&gt; dbus-devel[== 1.4.1-3.mga1]
+</I>&gt;&gt;<i> &gt;&gt; [...]
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; WDYT?
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; (If we agree to go one way or the other, will just fix them gradually
+</I>&gt;&gt;<i> &gt;&gt; over time).
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;&gt; --
+</I>&gt;&gt;<i> &gt;&gt; Ahmad Samir
+</I>&gt;&gt;<i> &gt;&gt;
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; Adding to the above, spturtle has suggested using pkgconfig()
+</I>&gt;&gt;<i> &gt; provides: <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2065">https://bugs.mageia.org/show_bug.cgi?id=2065</A>
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; --
+</I>&gt;&gt;<i> &gt; Ahmad Samir
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Using pkgconfig provides looks like an optimal option, we could start
+</I>&gt;&gt;<i> now, whenever we touch a spec we change to the pkgconfig provides, and
+</I>&gt;&gt;<i> gradually all the specs will be adapted.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> And for the packages that don't have .pc files we add:
+</I>&gt;&gt;<i> Provides: %{name}-devel = %{version}-release
+</I>&gt;&gt;<i> Provides: lib%{name}-devel = %{version}-release
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> or we could add them to all packages whether they have .pc files or
+</I>&gt;&gt;<i> not, but still always use pkgconfig() provides as BR in our specs.
+</I>&gt;<i>
+</I>&gt;<i> I think it's better to use %{name}-devel for packages which don't have
+</I>&gt;<i> pkgconfig files. And keep pkgconfig() provides for packages with .pc
+</I>&gt;<i> files.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>
+As spturtle said, conformity/consistency is good, i.e. all our
+packages should have the same Provides, that's better in the long run,
+and less confusing for new (and old too) packagers.
+
+The cost of dropping lib%{name}-devel altogether is some specs may
+break, but that can be mitigated by adding the SRPMS repos manually (I
+didn't know those repos had hdlists, until tv pointed it out in
+another thread some time ago), and checking:
+urpmf --media Core-SRPMS --requires lib%{name}-devel
+
+and then fixing all the specs that has lib%{name}-devel (that may be a
+daunting task sometimes, though).
+
+The point is, we don't have to fix this tomorrow, we start now and
+with mga2/3 all the specs will have been cleaned up.
+
+--
+Ahmad Samir
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006602.html">[Mageia-dev] Standardising the virtual Provides in -devel packages
+</A></li>
+ <LI>Next message: <A HREF="006879.html">[Mageia-dev] Standardising the virtual Provides in -devel packages
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6603">[ date ]</a>
+ <a href="thread.html#6603">[ thread ]</a>
+ <a href="subject.html#6603">[ subject ]</a>
+ <a href="author.html#6603">[ 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>