GNOME Bugzilla – Bug 783129
Update jhbuild modulesets for glibmm and cairomm
Last modified: 2017-05-31 19:07:44 UTC
Currently jhbuild's module "glibmm" refers to branch "glibmm-2-52". I believe this is now considered a stable-ish branch, i.e. part of module "glibmm-2.4". If so, then given that "glibmm" is the next/development version, it should use git branch "glibmm-2-54". Also, pangomm and gtkmm look for glibmm-2.54.pc, but glibmm's configure.ac has GLIBMM_MODULE_NAME == "glibmm", so the pkg-config file cannot be found when trying to build such dependent packages. At least I think that's why it's not working. Or am I doing something wrong? My jhbuild has gotten a bit hosed recently, so it's certainly possible...
(In reply to Daniel Boles from comment #0) > Currently jhbuild's module "glibmm" refers to branch "glibmm-2-52". I > believe this is now considered a stable-ish branch, i.e. part of module > "glibmm-2.4". If so, then given that "glibmm" is the next/development > version, it should use git branch "glibmm-2-54". Er. Master, even. > Also, pangomm and gtkmm look for glibmm-2.54.pc, but glibmm's configure.ac > has GLIBMM_MODULE_NAME == "glibmm", so the pkg-config file cannot be found > when trying to build such dependent packages. At least I think that's why > it's not working. This should be fixed once the right branch is being used, with the module name updated in it.
(In reply to Daniel Boles from comment #0) > Currently jhbuild's module "glibmm" refers to branch "glibmm-2-52". For module "glibmm", this is only the case for moduleset version 3.24. For 3.26, no branch is specified, so it will use master. Should this be changed in 3.24, too? I'm still not quite clear on how/when jhbuild modulesets are split off from each other. For module "glibmm-2-4", both 3.24 and 3.26 point at branch "glibmm-2-50". Should this be updated to "glibmm-2-52" in just moduleset version 3.26, or also 3.24?
Next up, master gdkmm depends on cairomm >= 1.15.4, but the 3.26 moduleset downloads a tar of 1.15.3, and there is no tar of 1.15.4 on the website. Should this just be pointed at master, or should a tar be uploaded?
Created attachment 352665 [details] [review] core-deps-3.26: Update branch of stable glibmm-2.4 The branch glibmm-2-52 is now considered part of the stable glibmm-2.4 ABI/module, so we should update to that.
Created attachment 352666 [details] [review] core-deps-3.26: Get cairomm from git master Until a tarball of version 1.15.4 is published. gtkmm master needs this version to build.
These fixed the problems for me, so unless anyone has any objections, I think it's safe enough (certainly an improvement!) to push these later.
Attachment 352665 [details] pushed as b4f9f9a - core-deps-3.26: Update branch of stable glibmm-2.4 Attachment 352666 [details] pushed as 14b26d6 - core-deps-3.26: Get cairomm from git master