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 08:19:58 +0200 [thread overview]
Message-ID: <20200712061958.p0_SQMRuiClsoxCMVWbOAWw7vDJurjFOBR9cFx1up1U@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: 1266 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/23530#issuecomment-657180842
Comment:
Update: adding a dependency on `adwaita-icon-theme` will create a build dependency cycle because that package depends on `librsvg`, which depends on `gtk+3-devel` to build.
I cleaned up the `adwaita-icon-theme` template here, noticing the the package builds *exactly* the same without any of the `hostmakedepends` I removed. Also, the flag in `configure_args` is no longer recognized by the configure script.
The last change is to remove `librsvg` from `depends` to break the build cycle. `adwaita-icon-theme` provides SVG versions of its theme and I understand that `librsvg` will be needed to support the scalable theme. However, I believe this support is optional and maybe shouldn't trump the availability of a default theme as a hard dependency on `gtk+3`. Also, I'd argue that the requirement to be able to read SVG files rests not with the theme that provides them, but with the package that reads the them.
If dropping the `librsvg` dep is unacceptable, we have no choice but to drop the `adwaita` dep from `gtk+3` and will always have the problem that `gtk+3` programs may not display properly by default.
next prev parent reply other threads:[~2020-07-12 6:20 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 [this message]
2020-07-12 15:36 ` ericonr
2020-07-12 17:16 ` ahesford
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=20200712061958.p0_SQMRuiClsoxCMVWbOAWw7vDJurjFOBR9cFx1up1U@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).