public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: kde-apps/spectacle/
Date: Wed, 19 Jun 2024 12:46:29 +0000 (UTC)	[thread overview]
Message-ID: <1718801151.5f29c10942ce40cdf5647e04ea57998474863615.sam@gentoo> (raw)

commit:     5f29c10942ce40cdf5647e04ea57998474863615
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 19 12:45:51 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 19 12:45:51 2024 +0000
URL:        https://gitweb.gentoo.org/proj/kde.git/commit/?id=5f29c109

kde-apps/spectacle: LTO is now safe on master

See upstream commit aa55610fdb5dbf38bdc2796f179745b826d1e7a2.

Bug: https://bugs.gentoo.org/932501
Signed-off-by: Sam James <sam <AT> gentoo.org>

 kde-apps/spectacle/spectacle-9999.ebuild | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/kde-apps/spectacle/spectacle-9999.ebuild b/kde-apps/spectacle/spectacle-9999.ebuild
index 694dd7df2a..34ddfaa0d1 100644
--- a/kde-apps/spectacle/spectacle-9999.ebuild
+++ b/kde-apps/spectacle/spectacle-9999.ebuild
@@ -9,7 +9,7 @@ KDE_GCC_MINIMAL=13
 PVCUT=$(ver_cut 1-3)
 KFMIN=6.3.0
 QTMIN=6.6.2
-inherit ecm flag-o-matic gear.kde.org
+inherit ecm gear.kde.org
 
 DESCRIPTION="Screenshot capture utility"
 HOMEPAGE="https://apps.kde.org/spectacle/"
@@ -64,10 +64,6 @@ BDEPEND="
 "
 
 src_configure() {
-	# bug #932501
-	filter-lto
-	append-flags -fno-strict-aliasing
-
 	local mycmakeargs=(
 		$(cmake_use_find_package share KF6Purpose)
 	)


             reply	other threads:[~2024-06-19 12:46 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 12:46 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-16 21:52 [gentoo-commits] proj/kde:master commit in: kde-apps/spectacle/ Andreas Sturmlechner
2025-03-16 21:52 Andreas Sturmlechner
2025-03-16 21:52 Andreas Sturmlechner
2025-03-15 21:41 Andreas Sturmlechner
2024-11-10 16:46 Andreas Sturmlechner
2024-11-04 23:01 Andreas Sturmlechner
2024-08-24 17:19 Sam James
2024-08-09 17:30 Andreas Sturmlechner
2024-06-20 14:25 Sam James
2024-06-17 16:04 Andreas Sturmlechner
2024-06-16  2:43 Sam James
2024-05-16 14:26 Andreas Sturmlechner
2024-04-22 20:41 Andreas Sturmlechner
2024-03-15 14:07 Andreas Sturmlechner
2024-02-27 22:08 Andreas Sturmlechner
2024-02-25 19:24 Sam James
2024-01-11 18:19 Sam James
2023-12-09 10:03 Andreas Sturmlechner
2023-03-23 22:10 Andreas Sturmlechner
2023-02-24  9:04 Andreas Sturmlechner
2023-02-23 20:25 Andreas Sturmlechner
2022-03-21 20:40 Andreas Sturmlechner
2022-03-21 20:40 Andreas Sturmlechner
2022-03-21 11:23 Andreas Sturmlechner
2022-03-21 10:43 Andreas Sturmlechner
2022-03-15 21:59 Andreas Sturmlechner
2022-03-15 21:59 Andreas Sturmlechner
2021-12-21  3:57 Sam James
2021-12-09  9:28 Andreas Sturmlechner
2021-02-26 13:09 Andreas Sturmlechner
2021-01-08  0:00 Andreas Sturmlechner
2020-02-08 20:02 Andreas Sturmlechner
2019-09-08 18:23 Andreas Sturmlechner
2019-07-17 18:19 Andreas Sturmlechner
2019-06-22 11:40 Andreas Sturmlechner
2019-05-08  6:09 Andreas Sturmlechner
2019-03-26 22:01 Andreas Sturmlechner
2018-08-15 17:40 Andreas Sturmlechner
2018-08-06 23:59 Andreas Sturmlechner
2016-12-11 19:13 Michael Palimaka
2016-11-27 11:30 Michael Palimaka
2016-10-20 20:55 Michael Palimaka
2016-08-25 18:15 Michael Palimaka
2016-08-25 18:15 Michael Palimaka
2016-05-31 19:03 Johannes Huber
2016-04-24 18:08 Manuel Rüger
2016-03-25 14:00 Michael Palimaka
2016-03-08 10:25 Michael Palimaka
2016-03-08 10:25 Michael Palimaka
2016-01-20 14:52 Michael Palimaka
2016-01-20 14:52 Michael Palimaka
2016-01-04 16:21 Michael Palimaka
2016-01-02 15:36 Michael Palimaka
2016-01-01 16:28 Michael Palimaka
2015-11-14 16:03 Michael Palimaka
2015-11-13 16:52 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=1718801151.5f29c10942ce40cdf5647e04ea57998474863615.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