From: "Ronny Gutbrod" <gentoo@tastytea.de>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-util/blueprint-compiler/
Date: Wed, 23 Feb 2022 00:33:48 +0000 (UTC) [thread overview]
Message-ID: <1645448982.0e4a1a1043d43b0c2c6c8b4e4eb9dd91511fa366.tastytea@gentoo> (raw)
commit: 0e4a1a1043d43b0c2c6c8b4e4eb9dd91511fa366
Author: Yuan Liao <liaoyuan <AT> gmail <DOT> com>
AuthorDate: Mon Feb 21 13:05:20 2022 +0000
Commit: Ronny Gutbrod <gentoo <AT> tastytea <DOT> de>
CommitDate: Mon Feb 21 13:09:42 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=0e4a1a10
dev-util/blueprint-compiler: Add missing test dependency
Closes: https://bugs.gentoo.org/833823
Signed-off-by: Yuan Liao <liaoyuan <AT> gmail.com>
.../blueprint-compiler-0.1.0_pre20220219.ebuild | 9 ++++++++-
dev-util/blueprint-compiler/blueprint-compiler-9999.ebuild | 9 ++++++++-
2 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/dev-util/blueprint-compiler/blueprint-compiler-0.1.0_pre20220219.ebuild b/dev-util/blueprint-compiler/blueprint-compiler-0.1.0_pre20220219.ebuild
index 6dfccd58c..f38e5e7d8 100644
--- a/dev-util/blueprint-compiler/blueprint-compiler-0.1.0_pre20220219.ebuild
+++ b/dev-util/blueprint-compiler/blueprint-compiler-0.1.0_pre20220219.ebuild
@@ -28,8 +28,9 @@ HOMEPAGE="https://jwestman.pages.gitlab.gnome.org/blueprint-compiler/"
LICENSE="LGPL-3+"
SLOT="0"
-IUSE="doc"
+IUSE="doc test"
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
+RESTRICT="!test? ( test )"
BDEPEND="
${PYTHON_DEPS}
@@ -39,6 +40,12 @@ BDEPEND="
)
"
+DEPEND="
+ test? (
+ gui-libs/gtk:4[introspection]
+ )
+"
+
RDEPEND="
${PYTHON_DEPS}
"
diff --git a/dev-util/blueprint-compiler/blueprint-compiler-9999.ebuild b/dev-util/blueprint-compiler/blueprint-compiler-9999.ebuild
index 7ffa8d633..219419000 100644
--- a/dev-util/blueprint-compiler/blueprint-compiler-9999.ebuild
+++ b/dev-util/blueprint-compiler/blueprint-compiler-9999.ebuild
@@ -28,8 +28,9 @@ HOMEPAGE="https://jwestman.pages.gitlab.gnome.org/blueprint-compiler/"
LICENSE="LGPL-3+"
SLOT="0"
-IUSE="doc"
+IUSE="doc test"
REQUIRED_USE="${PYTHON_REQUIRED_USE}"
+RESTRICT="!test? ( test )"
BDEPEND="
${PYTHON_DEPS}
@@ -39,6 +40,12 @@ BDEPEND="
)
"
+DEPEND="
+ test? (
+ gui-libs/gtk:4[introspection]
+ )
+"
+
RDEPEND="
${PYTHON_DEPS}
"
next reply other threads:[~2022-02-23 0:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 0:33 Ronny Gutbrod [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-14 16:35 [gentoo-commits] repo/proj/guru:master commit in: dev-util/blueprint-compiler/ Florian Schmaus
2023-01-26 8:58 Florian Schmaus
2023-01-26 8:58 Florian Schmaus
2022-12-06 6:09 Viorel Munteanu
2022-12-01 3:59 Haelwenn Monnier
2022-12-01 3:59 Haelwenn Monnier
2022-12-01 3:59 Haelwenn Monnier
2022-12-01 3:59 Haelwenn Monnier
2022-09-17 11:49 Ronny Gutbrod
2022-09-17 11:49 Ronny Gutbrod
2022-08-02 10:55 Haelwenn Monnier
2022-07-07 7:33 Haelwenn Monnier
2022-06-13 10:49 Andrew Ammerlaan
2022-06-13 10:49 Andrew Ammerlaan
2022-06-13 10:49 Andrew Ammerlaan
2022-03-25 11:24 Ronny Gutbrod
2022-02-20 8:46 Florian Schmaus
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=1645448982.0e4a1a1043d43b0c2c6c8b4e4eb9dd91511fa366.tastytea@gentoo \
--to=gentoo@tastytea.de \
--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