From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: kde-frameworks/breeze-icons/
Date: Wed, 18 Jun 2025 19:00:30 +0000 (UTC) [thread overview]
Message-ID: <1750273218.2d67f882ab5deb35b653ab110e6fb52ea0031a34.sam@gentoo> (raw)
commit: 2d67f882ab5deb35b653ab110e6fb52ea0031a34
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:00:18 2025 +0000
URL: https://gitweb.gentoo.org/proj/kde.git/commit/?id=2d67f882
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.
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-9999.ebuild | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/kde-frameworks/breeze-icons/breeze-icons-9999.ebuild b/kde-frameworks/breeze-icons/breeze-icons-9999.ebuild
index 700989165d..e6b1cef3ab 100644
--- a/kde-frameworks/breeze-icons/breeze-icons-9999.ebuild
+++ b/kde-frameworks/breeze-icons/breeze-icons-9999.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"
@@ -31,6 +31,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:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 19:00 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-20 5:03 [gentoo-commits] proj/kde:master commit in: kde-frameworks/breeze-icons/ Sam James
2024-07-13 20:35 Sam James
2024-07-12 19:58 Andreas Sturmlechner
2024-06-11 19:34 Andreas Sturmlechner
2024-06-11 19:34 Andreas Sturmlechner
2024-05-16 1:44 Sam James
2024-05-13 20:40 Andreas Sturmlechner
2024-05-13 20:40 Andreas Sturmlechner
2024-02-27 16:07 Andreas Sturmlechner
2024-02-25 10:32 Andreas Sturmlechner
2023-12-28 17:31 Andreas Sturmlechner
2023-12-21 16:15 Sam James
2023-08-15 14:33 Andreas Sturmlechner
2022-08-11 10:19 Sam James
2022-07-03 10:55 Andreas Sturmlechner
2022-06-10 7:52 Andreas Sturmlechner
2021-10-02 15:19 Andreas Sturmlechner
2021-05-20 21:04 Andreas Sturmlechner
2020-07-12 23:09 Andreas Sturmlechner
2019-11-11 7:30 Andreas Sturmlechner
2019-10-16 13:21 Andreas Sturmlechner
2019-05-16 8:55 Michael Palimaka
2017-01-22 18:54 Michael Palimaka
2016-10-21 19:40 Michael Palimaka
2016-09-10 20:29 Manuel Rüger
2016-03-26 18:16 Michael Palimaka
2016-01-10 23:36 Manuel Rüger
2015-11-10 17:05 Michael Palimaka
2015-11-09 14:38 Michael Palimaka
2015-11-09 14:15 Michael Palimaka
2015-11-09 14:12 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=1750273218.2d67f882ab5deb35b653ab110e6fb52ea0031a34.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