From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/cutter/
Date: Mon, 8 Aug 2022 09:40:33 +0000 (UTC) [thread overview]
Message-ID: <1659951618.79b87b5b8b7c5b736ed8362f348fa76ec3982ea6.asturm@gentoo> (raw)
commit: 79b87b5b8b7c5b736ed8362f348fa76ec3982ea6
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 25 17:35:55 2022 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Mon Aug 8 09:40:18 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=79b87b5b
dev-util/cutter: Move dev-qt/linguist-tools:5 to BDEPEND
Bug: https://bugs.gentoo.org/544938
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
dev-util/cutter/cutter-2.1.0.ebuild | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/dev-util/cutter/cutter-2.1.0.ebuild b/dev-util/cutter/cutter-2.1.0.ebuild
index 4c7fdfec26b1..706ec46206de 100644
--- a/dev-util/cutter/cutter-2.1.0.ebuild
+++ b/dev-util/cutter/cutter-2.1.0.ebuild
@@ -19,7 +19,7 @@ KEYWORDS="amd64 ~x86"
IUSE="graphviz"
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
-COMMON_DEPEND="${PYTHON_DEPS}
+DEPEND="${PYTHON_DEPS}
dev-qt/qtcore:5
dev-qt/qtgui:5
dev-qt/qtnetwork:5
@@ -27,9 +27,8 @@ COMMON_DEPEND="${PYTHON_DEPS}
dev-qt/qtwidgets:5
>=dev-util/rizin-0.4.0:=
graphviz? ( media-gfx/graphviz )"
-DEPEND="${COMMON_DEPEND}
- dev-qt/linguist-tools:5"
-RDEPEND="${COMMON_DEPEND}"
+RDEPEND="${DEPEND}"
+BDEPEND="dev-qt/linguist-tools:5"
src_prepare() {
rmdir "${S}/src/translations" || die
next reply other threads:[~2022-08-08 9:40 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 9:40 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-11 18:23 [gentoo-commits] repo/gentoo:master commit in: dev-util/cutter/ Andreas Sturmlechner
2025-02-10 19:01 Arthur Zamarin
2025-01-14 4:02 John Helmert III
2025-01-12 22:24 John Helmert III
2025-01-12 22:24 John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28 2:39 Sam James
2024-05-11 19:08 Sam James
2024-04-21 23:33 John Helmert III
2024-03-04 5:21 John Helmert III
2024-03-04 5:21 John Helmert III
2023-09-26 0:54 Sam James
2023-09-17 0:06 John Helmert III
2023-09-10 18:04 John Helmert III
2023-07-22 16:30 John Helmert III
2023-07-22 16:30 John Helmert III
2023-07-22 16:30 John Helmert III
2023-06-02 4:04 John Helmert III
2023-04-30 23:36 John Helmert III
2023-04-30 23:36 John Helmert III
2023-04-16 18:52 John Helmert III
2023-02-25 16:35 John Helmert III
2023-02-23 3:55 John Helmert III
2023-02-22 15:58 John Helmert III
2022-10-21 19:56 John Helmert III
2022-10-21 19:56 John Helmert III
2022-09-11 13:33 John Helmert III
2022-09-10 21:22 John Helmert III
2022-07-04 20:01 John Helmert III
2022-07-04 20:01 John Helmert III
2022-07-04 20:01 John Helmert III
2022-03-02 2:43 John Helmert III
2022-03-02 2:43 John Helmert III
2022-01-14 20:35 John Helmert III
2021-12-01 16:22 John Helmert III
2021-11-20 23:30 John Helmert III
2021-10-17 16:08 John Helmert III
2021-10-15 16:57 Rick Farina
2021-10-05 20:40 John Helmert III
2021-05-24 23:37 John Helmert III
2021-05-24 23:37 John Helmert III
2021-04-27 3:15 John Helmert III
2021-04-14 19:26 John Helmert III
2021-04-11 22:31 John Helmert III
2021-04-06 19:03 Sergei Trofimovich
2021-04-06 13:08 John Helmert III
2021-04-06 2:59 John Helmert III
2020-10-18 12:31 Sergei Trofimovich
2020-09-03 22:28 Sergei Trofimovich
2020-07-25 5:44 Joonas Niilola
2020-07-25 5:30 Joonas Niilola
2020-07-25 5:30 Joonas Niilola
2020-07-25 5:30 Joonas Niilola
2020-07-24 8:28 Joonas Niilola
2019-08-12 20:16 Michał Górny
2019-07-07 19:17 Michał Górny
2018-01-25 11:16 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=1659951618.79b87b5b8b7c5b736ed8362f348fa76ec3982ea6.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