[RFC] pango: update to 1.46.1

[q66]

Since about a year ago, we've been holding back the pango version at now long obsolete 1.42 series, as pango upstream's move to harfbuzz resulted in bitmap font formats no longer working. This is now starting to become increasingly problematic, for various reasons:

1. some parts of the upcoming GNOME 3.38 update depend on newer versions and require clunky patching otherwise
2. the soon upcoming Gtk 4.0 stable release (why do we have a very old alpha version of that packaged anyway, nothing currently depends on it?) carries a hard dependency on much newer Pango and there is no hope of backporting things
3. the old Pango has some code paths with fairly poor performance that have improved since
4. it means things such as the librsvg testsuite fail, because of a different text shaping behavior between the versions

IMO this is not our problem. A year should've been more than enough time for people to fix/adjust their setups, and if they still have problems with it, they should take it to upstream - it's not our issue to solve. Keeping things at the older version is not sustainable, and the issue only affects a small minority of users, so I just wouldn't bother.

@void-linux/pkg-committers

[ahesford]

With a rolling-release approach comes the occasional backwards incompatibility. Why should pango be a special case? Update the package.

[pullmoll]

We should not stop updating packages to newer versions as a convenience service for users. So yes, let's update pango.

[sirikid]

why do we have a very old alpha version of that packaged anyway, nothing currently depends on it?

I would ask 'why do we have it' in a first place. I packaged the latest alpha when experimenting with emacs-pgtk. emacs-pgtk was unusable for me, so in the end I didn't submit any updates.