From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: kde-apps/kalarm/
Date: Thu, 29 Aug 2024 15:25:33 +0000 (UTC) [thread overview]
Message-ID: <1724945058.5c3e2db23a989cfa953f6d38e6e20096d4252722.asturm@gentoo> (raw)
commit: 5c3e2db23a989cfa953f6d38e6e20096d4252722
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 28 18:42:45 2024 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Thu Aug 29 15:24:18 2024 +0000
URL: https://gitweb.gentoo.org/proj/kde.git/commit/?id=5c3e2db2
kde-apps/kalarm: Workaround implicit CMake dependency chain issue
- USE=-speech sets -DCMAKE_DISABLE_FIND_PACKAGE_KF6TextEditTextToSpeech=ON
- kde-apps/kidentitymanagement depends on kde-apps/kpimtextedit
- If kde-apps/kpimtextedit was built with USE=speech, its cmake config file
depends on KF6TextEditTextToSpeech which then fails to be found when
disabled by the kde-apps/kalarm[-speech] cmake arg.
Bug: https://bugs.gentoo.org/934478
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
kde-apps/kalarm/kalarm-24.08.49.9999.ebuild | 1 +
kde-apps/kalarm/kalarm-9999.ebuild | 1 +
2 files changed, 2 insertions(+)
diff --git a/kde-apps/kalarm/kalarm-24.08.49.9999.ebuild b/kde-apps/kalarm/kalarm-24.08.49.9999.ebuild
index 3024bd47e8..d4b4acfaa8 100644
--- a/kde-apps/kalarm/kalarm-24.08.49.9999.ebuild
+++ b/kde-apps/kalarm/kalarm-24.08.49.9999.ebuild
@@ -63,6 +63,7 @@ RDEPEND="${COMMON_DEPEND}
pim? ( >=kde-apps/kdepim-runtime-${PVCUT}:6 )
"
DEPEND="${COMMON_DEPEND}
+ speech? ( kde-apps/kpimtextedit[speech] )
X? ( x11-base/xorg-proto )
"
diff --git a/kde-apps/kalarm/kalarm-9999.ebuild b/kde-apps/kalarm/kalarm-9999.ebuild
index 1b5e57efc6..860e0432c7 100644
--- a/kde-apps/kalarm/kalarm-9999.ebuild
+++ b/kde-apps/kalarm/kalarm-9999.ebuild
@@ -64,6 +64,7 @@ RDEPEND="${COMMON_DEPEND}
pim? ( >=kde-apps/kdepim-runtime-${PVCUT}:6 )
"
DEPEND="${COMMON_DEPEND}
+ speech? ( kde-apps/kpimtextedit[speech] )
X? ( x11-base/xorg-proto )
"
next reply other threads:[~2024-08-29 15:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 15:25 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-22 21:11 [gentoo-commits] proj/kde:master commit in: kde-apps/kalarm/ Sam James
2025-03-04 22:59 Andreas Sturmlechner
2024-11-10 22:52 Andreas Sturmlechner
2024-09-12 19:30 Andreas Sturmlechner
2024-08-11 6:58 Andreas Sturmlechner
2024-08-10 18:53 Andreas Sturmlechner
2024-05-20 21:57 Andreas Sturmlechner
2024-05-17 19:50 Andreas Sturmlechner
2024-03-03 15:05 Andreas Sturmlechner
2024-02-25 22:58 Sam James
2023-07-06 12:00 Andreas Sturmlechner
2022-12-05 18:33 Andreas Sturmlechner
2022-07-08 12:55 Andreas Sturmlechner
2022-03-24 14:53 Andreas Sturmlechner
2021-11-15 10:59 Andreas Sturmlechner
2021-11-15 10:59 Andreas Sturmlechner
2021-04-25 8:00 Andreas Sturmlechner
2021-04-15 22:32 Andreas Sturmlechner
2020-10-26 13:56 Andreas Sturmlechner
2020-09-25 5:49 Andreas Sturmlechner
2020-06-15 11:26 Andreas Sturmlechner
2020-05-19 11:20 Andreas Sturmlechner
2019-08-08 22:18 Andreas Sturmlechner
2019-02-09 14:26 Andreas Sturmlechner
2018-08-16 20:26 Andreas Sturmlechner
2018-05-13 16:02 Andreas Sturmlechner
2016-08-31 14:33 Michael Palimaka
2016-05-11 9:51 Michael Palimaka
2016-04-02 22:15 Johannes Huber
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=1724945058.5c3e2db23a989cfa953f6d38e6e20096d4252722.asturm@gentoo \
--to=asturm@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