From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: subpixel rendering is broken in GTK programs
Date: Thu, 30 Jul 2020 17:26:01 +0200 [thread overview]
Message-ID: <20200730152601.z9m4VruboizK3JKdl5wVpUAsHE_-fPgsYyR1FlNoGTg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21429@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/21429#issuecomment-666454568
Comment:
@andry-dev @mvf
I see. If we can fix this with a config file, I'd be fine with the change as well. I mostly want to avoid having broken out of the box setups. Can either of you make a PR for it? I don't think I would be able to properly justify it myself.
That said, Void does have the policy of avoiding patching packages for functionality (kind of like Arch), which makes the fact that bigger distros have it enabled not entirely relevant to us. If possible, I would like to have this change turned into a `vsed` call and conditional installation of the config file, so it can be easily turned into a build option (which can even be enabled by default), but I'm not sure the commiters would agree.
next prev parent reply other threads:[~2020-07-30 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 14:21 [ISSUE] " VoidDuck
2020-04-29 6:43 ` travankor
2020-05-01 12:45 ` bsduck
2020-05-06 4:27 ` ericonr
2020-05-09 12:05 ` travankor
2020-05-09 12:06 ` travankor
2020-05-09 12:06 ` travankor
2020-07-29 23:31 ` ericonr
2020-07-30 5:55 ` mvf
2020-07-30 10:00 ` andry-dev
2020-07-30 10:01 ` andry-dev
2020-07-30 15:26 ` ericonr [this message]
2022-04-16 2:02 ` github-actions
2022-07-18 2:13 ` github-actions
2022-08-01 2:14 ` [ISSUE] [CLOSED] " github-actions
2023-02-20 1:13 ` bsduck
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=20200730152601.z9m4VruboizK3JKdl5wVpUAsHE_-fPgsYyR1FlNoGTg@z \
--to=ericonr@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).