Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gtk+3: update to 3.24.21.
Date: Sun, 12 Jul 2020 19:16:54 +0200	[thread overview]
Message-ID: <20200712171654.ruCzmMgmv4SiPEHDlNo-k8bpezvVyMRkl4qXAQStdk4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23530@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/23530#issuecomment-657251223

Comment:
Having `gtk+3` depend on `librsvg` would be the best solution, but it isn't realizable because `librsvg` depends on `gtk+3-devel` and would create a build-time dependency cycle.

I may explore breaking this cycle. Maybe splitting Adwaita into separate PNG-only and SVG-only themes would allow GTK to depend on the PNG-only themes that would work everywhere, with users having the option to install the SVG theme if they were interested.

We could also just discard the SVG files to provide a basic functional PNG theme for GTK, then tell users we don't package SVG for the same reason we are refusing to package other themes. 

  parent reply	other threads:[~2020-07-12 17:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-12  3:53 [PR PATCH] " ahesford
2020-07-12  6:07 ` [PR PATCH] [Updated] " ahesford
2020-07-12  6:19 ` ahesford
2020-07-12 15:36 ` ericonr
2020-07-12 17:16 ` ahesford [this message]
2020-07-12 18:12 ` [PR PATCH] [Updated] [NOMERGE] " ahesford
2020-07-12 18:17 ` ahesford
2020-07-12 21:56 ` ericonr
2020-07-13  2:38 ` ahesford
2020-07-13  8:12 ` fosslinux
2020-07-15 23:54 ` ahesford
2020-07-15 23:54 ` [PR PATCH] [Merged]: " ahesford

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=20200712171654.ruCzmMgmv4SiPEHDlNo-k8bpezvVyMRkl4qXAQStdk4@z \
    --to=ahesford@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).