From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/breeze-icons/
Date: Wed, 18 Jun 2025 19:03:55 +0000 (UTC) [thread overview]
Message-ID: <1750273359.9582bcb70d3c14a67778459ad3409c2260ad294d.sam@gentoo> (raw)
commit: 9582bcb70d3c14a67778459ad3409c2260ad294d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 18 19:00:01 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 18 19:02:39 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9582bcb7
kde-frameworks/breeze-icons: filter LTO again
There's a trade-off between allowing LTO upstream vs supporting
compilation with less RAM available because of how Qt resources work.
See https://mail.kde.org/pipermail/distributions/2025-June/001602.html.
(We backported the upstream fix for 32-bit systems to 6.15.0
in 1a6c9b23d83e6138e7ecf391b7cfa67cb88100f3.)
Bug: https://bugs.gentoo.org/931904
Bug: https://bugs.gentoo.org/956679
Signed-off-by: Sam James <sam <AT> gentoo.org>
kde-frameworks/breeze-icons/breeze-icons-6.15.0.ebuild | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/kde-frameworks/breeze-icons/breeze-icons-6.15.0.ebuild b/kde-frameworks/breeze-icons/breeze-icons-6.15.0.ebuild
index 8668c832ca42..18bcadc45f10 100644
--- a/kde-frameworks/breeze-icons/breeze-icons-6.15.0.ebuild
+++ b/kde-frameworks/breeze-icons/breeze-icons-6.15.0.ebuild
@@ -4,7 +4,7 @@
EAPI=8
PYTHON_COMPAT=( python3_{10..13} )
-inherit cmake frameworks.kde.org python-any-r1 xdg
+inherit cmake flag-o-matic frameworks.kde.org python-any-r1 xdg
DESCRIPTION="Breeze SVG icon theme"
@@ -33,6 +33,11 @@ python_check_deps() {
}
src_configure() {
+ # There's a trade-off between allowing LTO upstream vs supporting
+ # compilation with less RAM available because of how Qt resources work.
+ # See bug #931904 and bug #956679.
+ filter-lto
+
local mycmakeargs=(
-DPython_EXECUTABLE="${PYTHON}"
-DBINARY_ICONS_RESOURCE=ON # TODO: remove when kexi was ported away
next reply other threads:[~2025-06-18 19:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 19:03 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-01 22:26 [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/breeze-icons/ Andreas Sturmlechner
2025-03-15 20:56 Andreas Sturmlechner
2024-07-13 20:35 Sam James
2024-07-12 19:57 Andreas Sturmlechner
2024-05-16 1:45 Sam James
2024-02-27 16:10 Andreas Sturmlechner
2024-02-25 12:09 Andreas Sturmlechner
2023-12-28 17:39 Andreas Sturmlechner
2023-12-21 16:13 Sam James
2022-10-10 8:39 Andreas Sturmlechner
2022-08-11 9:49 Sam James
2022-06-28 4:18 WANG Xuerui
2021-12-15 13:55 Andreas Sturmlechner
2021-12-15 11:28 Andreas Sturmlechner
2021-10-02 15:18 Andreas Sturmlechner
2021-01-01 22:45 Andreas Sturmlechner
2020-07-12 23:07 Andreas Sturmlechner
2019-11-11 7:34 Andreas Sturmlechner
2019-05-16 8:56 Michael Palimaka
2018-10-10 11:48 Mikle Kolyada
2018-06-10 18:37 Thomas Deutschmann
2018-03-27 7:52 Sergei Trofimovich
2018-03-27 7:52 Sergei Trofimovich
2018-01-19 21:35 Andreas Sturmlechner
2017-07-25 18:14 Alexis Ballier
2017-01-22 18:52 Michael Palimaka
2016-10-13 10:27 Michael Palimaka
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=1750273359.9582bcb70d3c14a67778459ad3409c2260ad294d.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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