Bug 8584 - GTK/GLib and friends are old
Summary: GTK/GLib and friends are old
Status: RESOLVED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Build system (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.19.0
Assignee: Pierre Ossman
URL:
Keywords: prosaic
Depends on:
Blocks: 8361
  Show dependency treegraph
 
Reported: 2025-05-07 10:51 CEST by Pierre Ossman
Modified: 2025-05-13 11:12 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Pierre Ossman cendio 2025-05-07 10:51:18 CEST
Our packages from the GTK/GLib world in our build environment are rather old. Besides wanting new features and bug fixes, this also makes them block the upgrade of gcc (bug 8361).

Note that we only have GTK for Dia, which means it is GTK2. So the focus is more on the other related packages.
Comment 1 Pierre Ossman cendio 2025-05-09 10:12:25 CEST
Newer GLib and friends ideally need newer MinGW and newer macOS SDK. Fortunately, we can patch around it and get almost to the latest version.


As a side effect of this exploration, PCRE got upgraded as GLib used to require that. But even newer GLib switched to PCRE2 instead.

I'm keeping the PCRE upgrade, though, as the work is already done and we use it in other components.
Comment 2 Pierre Ossman cendio 2025-05-12 16:36:45 CEST
I've now updated (or added):

 * libffi
 * pcre
 * pcre2
 * glib
 * shared-mime-info
 * gobject-introspection
 * GTK+ 2.x
 * Docbook XSL stylesheets
 * fontconfig
 * libdatrie
 * libthai
 * fribidi
 * harfbuzz
 * help2man
 * pango

I checked that the images in the TAG still look okay (Dia uses a bunch of these libraries).

I tested smart card support (pcsctun uses GLib), and thinlocal (pango/freetype), and the client's UI (freetype/fontconfig).

Tested with a RHEL 8 server, and a Fedora 41, Windows 11, and macOS 15.4 clients.
Comment 35 Pierre Ossman cendio 2025-05-13 11:12:21 CEST
No significant user visible changes as part of this, so no release notes.

Note You need to log in before you can comment on or make changes to this bug.