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 --- .../20111116/d050d796/attachment-0001.html | 45 ++++++++++++++++++++++ .../attachments/20111116/d050d796/attachment.html | 45 ++++++++++++++++++++++ 2 files changed, 90 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20111116/d050d796') diff --git a/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html new file mode 100644 index 000000000..a81c6d704 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html @@ -0,0 +1,45 @@ + + + + + + + On 16/11/2011 10:44, Guillaume Rousse wrote: +
Le + 16/11/2011 00:11, jcc a écrit : +
+
Hi, +
+
+ I do not quite understand why with BuildRequires and Requires, + it is +
+ sometimes necessary to place a pkgconfig(any_lib) instead of + simply +
+ any_libin the spec file. +
+
+ If you have a dependency for any_lib, you'll only get the runtime + part of the lib. If you need to build something with the lib, + you'll need the buildtime part of the lib, which is generally + isolated in the -devel package. Hence the need for a build + dependency of either any_lib-devel (always present), or + pkgconfig(any_lib), which is a virtual package automatically + generated by rpm if a pkgconfig file is present. +
+
+
+
+

+
+
+
I thank you for these explanations.
+
+ Sincerely, J.-C.
+
+
+ + diff --git a/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html new file mode 100644 index 000000000..a81c6d704 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html @@ -0,0 +1,45 @@ + + + + + + + On 16/11/2011 10:44, Guillaume Rousse wrote: +
Le + 16/11/2011 00:11, jcc a écrit : +
+
Hi, +
+
+ I do not quite understand why with BuildRequires and Requires, + it is +
+ sometimes necessary to place a pkgconfig(any_lib) instead of + simply +
+ any_libin the spec file. +
+
+ If you have a dependency for any_lib, you'll only get the runtime + part of the lib. If you need to build something with the lib, + you'll need the buildtime part of the lib, which is generally + isolated in the -devel package. Hence the need for a build + dependency of either any_lib-devel (always present), or + pkgconfig(any_lib), which is a virtual package automatically + generated by rpm if a pkgconfig file is present. +
+
+
+
+

+
+
+
I thank you for these explanations.
+
+ Sincerely, J.-C.
+
+
+ + -- cgit v1.2.1