From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: [RFC] pango: update to 1.46.1
Date: Mon, 14 Sep 2020 16:15:25 +0200 [thread overview]
Message-ID: <20200914141525.IudjUslWu_Rox5FEYtoL1ZLhdNLWx-1mGTqre8xdJAs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24842@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
There's a merged pull request on the void-packages repository
[RFC] pango: update to 1.46.1
https://github.com/void-linux/void-packages/pull/24842
Description:
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
prev parent reply other threads:[~2020-09-14 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 2:29 [PR PATCH] " q66
2020-09-12 3:21 ` ahesford
2020-09-12 8:14 ` pullmoll
2020-09-13 21:21 ` sirikid
2020-09-14 14:15 ` q66 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200914141525.IudjUslWu_Rox5FEYtoL1ZLhdNLWx-1mGTqre8xdJAs@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).