summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20111116/d050d796
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20111116/d050d796')
-rw-r--r--zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment-0001.html45
-rw-r--r--zarb-ml/mageia-dev/attachments/20111116/d050d796/attachment.html45
2 files changed, 90 insertions, 0 deletions
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 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
+ </head>
+ <body text="#000000" bgcolor="#ffffff">
+ On 16/11/2011 10:44, Guillaume Rousse wrote:
+ <blockquote cite="mid:4EC38611.1040608@gmail.com" type="cite">Le
+ 16/11/2011 00:11, jcc a écrit :
+ <br>
+ <blockquote type="cite">Hi,
+ <br>
+ <br>
+ I do not quite understand why with BuildRequires and Requires,
+ it is
+ <br>
+ sometimes necessary to place a pkgconfig(any_lib) instead of
+ simply
+ <br>
+ any_libin the spec file.
+ <br>
+ </blockquote>
+ 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.
+ <br>
+ <br>
+ </blockquote>
+ <br>
+ <div style="width: 100%;"><br>
+ </div>
+ <div id="gt-res-content" class="almost_half_cell">
+ <div dir="ltr" style=""><span id="result_box" class="short_text"
+ lang="en"><span class="hps">I thank you for</span> <span
+ class="hps">these explanations.</span><br>
+ <br>
+ <span class="hps">Sincerely, J.-C.<br>
+ </span></span></div>
+ </div>
+ </body>
+</html>
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 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+ <head>
+ <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
+ </head>
+ <body text="#000000" bgcolor="#ffffff">
+ On 16/11/2011 10:44, Guillaume Rousse wrote:
+ <blockquote cite="mid:4EC38611.1040608@gmail.com" type="cite">Le
+ 16/11/2011 00:11, jcc a écrit :
+ <br>
+ <blockquote type="cite">Hi,
+ <br>
+ <br>
+ I do not quite understand why with BuildRequires and Requires,
+ it is
+ <br>
+ sometimes necessary to place a pkgconfig(any_lib) instead of
+ simply
+ <br>
+ any_libin the spec file.
+ <br>
+ </blockquote>
+ 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.
+ <br>
+ <br>
+ </blockquote>
+ <br>
+ <div style="width: 100%;"><br>
+ </div>
+ <div id="gt-res-content" class="almost_half_cell">
+ <div dir="ltr" style=""><span id="result_box" class="short_text"
+ lang="en"><span class="hps">I thank you for</span> <span
+ class="hps">these explanations.</span><br>
+ <br>
+ <span class="hps">Sincerely, J.-C.<br>
+ </span></span></div>
+ </div>
+ </body>
+</html>