Hi folks

On Sun, Dec 04, 2005, David Schmitt wrote:
> The manpage for pkg-config lacks a paragraph for Requires.private.
> Here is my shot at it:
> 
> Requires.private:
> This line should list any private packages in use. Private packages are
> packages which are not exposed through your library, but are needed in
> the case of static linking.
> 
> Libs.private could then be changed to reference this paragraph.

 Thanks for the proposed wording; I merged a similar wording in the git
 tree I prepared for Debian #475031, in the misc-requires-private-fixes
 branch:
    git.debian.org:/git/users/lool/pkg-config


  Cheers,


PS: here's the actual diff of the two commits

diff --git a/pkg-config.1 b/pkg-config.1
index b411e8b..5d39a17 100644
--- a/pkg-config.1
+++ b/pkg-config.1
@@ -388,6 +388,12 @@ checks. You may only mention the same package one time on t
 line. If the version of a package is unspecified, any version will
 be used with no checking.
 .TP
+.I "Requires.private:"
+This is a comma-separated list of private packages that are required by your
+package.  Private packages are packages which are needed for static linking or
+compile flags.  \fIRequires.private:\fP follows the same syntax as
+\fIRequires:\fP.
+.TP
 .I "Conflicts:"
 This optional line allows \fIpkg-config\fP to perform additional
 sanity checks, primarily to detect broken user installations.  The
@@ -410,7 +416,9 @@ add those automatically.
 .I "Libs.private:"
 This line should list any private libraries in use.  Private libraries
 are libraries which are not exposed through your library, but are
-needed in the case of static linking.
+needed in the case of static linking.  This differs from
+\fIRequires.private:\fP in that it references libraries that do not have
+package files installed.
 
 .TP
 .I "Cflags:"

-- 
Loïc Minier



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to