[Slackbuilds-users] Bluefish and glib2

[Willy Sudiarto Raharjo]

> Since nearly a month ago (I April 2025) I have upgraded glib2 to version 2.84.0
> (then, 2.84.1) in Slint (mainly based on Slackware64-125.0) reusing the
> SlackBuild from Slackware64-current without issue observed by me or reported by
> users.
> 
> I won't suggesting that this should or could be done by SBo, instead that as
> there is no ETA for for a new Slackware version doing that locally could help
> users upgrade some software.

while it does fix this particular issue, it will make another issue 
(just probably not yet discovered) as newer glib2 usually make changes 
that are NOT backward compatible with previous version

This is just one of the example
GLib 2.83.0, 2024-11-06
Rename multiple g_unix_mount_*() APIs to g_unix_mount_entry_*()
Update to Unicode 16.0.0; there may be bugs in linebreaking support

If the program is a toolchain, it's probably easier to create a new 
*-opt script which is newer than what we have in Slackware, like meson, 
setuptools, rust, etc. If it's library, we might end up with same 
situation when some scripts in SBo requires newer glib2/icu4c version in 
the future while the rest is not yet patched to support the newer version.


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250430/cd6fc3d8/attachment.asc>