GNOME Bugzilla – Bug 663421
pygtk-2.0.pc should include libdir=@libdir@
Last modified: 2018-08-17 13:35:14 UTC
if the pc includes libdir, it allows later variables to be based on it. this is useful if pyexecdir is set via ${libdir}/... simple patch: --- a/pygtk-2.0.pc.in +++ b/pygtk-2.0.pc.in @@ -3,6 +3,7 @@ includedir=@includedir@ datarootdir=@datarootdir@ datadir=@datadir@ +libdir=@libdir@ pyexecdir=@pyexecdir@ # you can use the --variable=pygtkincludedir argument to
Created attachment 233197 [details] [review] patch adding libdir to pygtk-2.0.pc.in
This is a breaker for me so I attached a formatted patch to increase chance of getting done.
i'd ping this bug (since it's still broken 4 years later w/one line patch), but it looks like pygtk is dead. last commit was 2.5 years ago, and that was to assign maintainership to someone who is inactive.
pygtk is not under active development anymore and had its last code changes in 2013. Its codebase has been archived: https://gitlab.gnome.org/Archive/pygtk/commits/master PyGObject at https://gitlab.gnome.org/GNOME/pygobject is its successor. See https://pygobject.readthedocs.io/en/latest/guide/porting.html for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent version of PyGObject. Thanks!