Bug 36162 - Make the pkgconfig dependency on glib/gobject public (Requires instead of Requires.private)
Summary: Make the pkgconfig dependency on glib/gobject public (Requires instead of Req...
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: git master
Hardware: Other All
: medium trivial
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL: http://cgit.freedesktop.org/~zabaluev...
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2011-04-12 06:41 UTC by Mikhail Zabaluev
Modified: 2019-12-03 20:38 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Mikhail Zabaluev 2011-04-12 06:41:01 UTC
The public headers of telepathy-glib include GObject headers and define inline primitives such as type casts that invoke functions from GObject. This technically makes the build-time dependency on GLib/GObject a public one, however for linkage these libraries may in some cases be non-essential. The commit offered for review corrects the pkg-config declarations.

NB: Generally speaking, pkg-config does not address this case precisely, and usage of Requires.private may be more beneficial to avoid useless linkage at runtime. But in case of telepathy-glib, it is reasonable to expect that most clients will use Telepathy type casts or invoke GLib/GObject directly as well.
Comment 1 Simon McVittie 2012-02-22 10:29:30 UTC
In Bug #15199 and <http://err.no/personal/blog/2008/Mar/25>, the maintainer of pkg-config told us not to apply an equivalent change, so...
Comment 2 GitLab Migration User 2019-12-03 20:38:06 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-glib/issues/62.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.