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-July/006598.html | 96 ++++++++++++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006598.html (limited to 'zarb-ml/mageia-dev/2011-July/006598.html') diff --git a/zarb-ml/mageia-dev/2011-July/006598.html b/zarb-ml/mageia-dev/2011-July/006598.html new file mode 100644 index 000000000..ce589ea22 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006598.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] Standardising the virtual Provides in -devel packages + + + + + + + + + +

[Mageia-dev] Standardising the virtual Provides in -devel packages

+ Sander Lepik + sander.lepik at eesti.ee +
+ Wed Jul 13 12:14:21 CEST 2011 +

+
+ +
13.07.2011 13:02, Ahmad Samir kirjutas:
+>
+> Using pkgconfig provides looks like an optimal option, we could start
+> now, whenever we touch a spec we change to the pkgconfig provides, and
+> gradually all the specs will be adapted.
+>
+> And for the packages that don't have .pc files we add:
+> Provides: %{name}-devel = %{version}-release
+> Provides: lib%{name}-devel = %{version}-release
+>
+> or we could add them to all packages whether they have .pc files or
+> not, but still always use pkgconfig() provides as BR in our specs.
+>
+> WDYT?
+>
++1
+
+IMHO provides should be added anyway.
+
+Who's gonna update policy? :)
+
+--
+Sander
+
+
+ + + + + + + + + + + + + + + + + + + +
+

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