public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git-machete/
Date: Thu,  1 Sep 2022 12:27:05 +0000 (UTC)	[thread overview]
Message-ID: <1662034331.fa5f56620752ee67894da067c9d23c7ee460b316.marecki@gentoo> (raw)

commit:     fa5f56620752ee67894da067c9d23c7ee460b316
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Thu Sep  1 12:12:11 2022 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Thu Sep  1 12:12:11 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fa5f5662

dev-vcs/git-machete: do not call python_gen_cond_dep

This was a holdover from the first, single-impl iteration of this ebuild.
Now that git-machete is installed multi-impl (and why not, maybe someone
WILL want to call it from Python scripts - the API is IMHO clean enough
for it to work), it is very much unnecessary.

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 dev-vcs/git-machete/git-machete-3.12.0.ebuild | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/dev-vcs/git-machete/git-machete-3.12.0.ebuild b/dev-vcs/git-machete/git-machete-3.12.0.ebuild
index fc280b8825d9..d84db41daa4c 100644
--- a/dev-vcs/git-machete/git-machete-3.12.0.ebuild
+++ b/dev-vcs/git-machete/git-machete-3.12.0.ebuild
@@ -19,10 +19,8 @@ KEYWORDS="~amd64 ~riscv"
 
 RDEPEND="dev-vcs/git"
 BDEPEND="test? (
-	$(python_gen_cond_dep '
-		>=dev-python/pytest-mock-3.8.2[${PYTHON_USEDEP}]
-		>=dev-python/pytest-xdist-2.5.0[${PYTHON_USEDEP}]
-	')
+	>=dev-python/pytest-mock-3.8.2[${PYTHON_USEDEP}]
+	>=dev-python/pytest-xdist-2.5.0[${PYTHON_USEDEP}]
 )"
 
 DOCS=( CONTRIBUTING.md README.md )


             reply	other threads:[~2022-09-01 12:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 12:27 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-24 12:58 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git-machete/ Marek Szuba
2024-04-15 12:20 Marek Szuba
2024-04-07  1:06 Marek Szuba
2023-12-27 15:29 Marek Szuba
2023-12-26 19:07 Sam James
2023-12-24 21:57 Marek Szuba
2023-10-24 23:16 Marek Szuba
2023-10-24 23:16 Marek Szuba
2023-10-24 23:16 Marek Szuba
2023-09-07  9:27 Marek Szuba
2023-08-28 21:26 Marek Szuba
2023-08-13 10:47 Marek Szuba
2023-08-12 21:07 Marek Szuba
2023-08-12 21:07 Marek Szuba
2023-08-12 21:07 Marek Szuba
2023-07-29 14:49 Marek Szuba
2023-07-10 23:04 Marek Szuba
2023-05-19  8:37 Marek Szuba
2023-05-11 12:03 Marek Szuba
2023-05-11 12:03 Marek Szuba
2023-05-11 12:03 Marek Szuba
2023-04-19  7:36 Marek Szuba
2023-04-05 21:20 Marek Szuba
2023-04-02 22:20 Marek Szuba
2023-03-13 12:02 Marek Szuba
2023-03-07 19:23 Marek Szuba
2023-03-07 11:42 Sam James
2023-03-06 22:37 Marek Szuba
2023-03-06 15:58 Marek Szuba
2023-02-21 23:41 Marek Szuba
2023-01-19 10:38 Marek Szuba
2022-11-10  0:42 Marek Szuba
2022-11-10  0:42 Marek Szuba
2022-10-21 10:20 Marek Szuba
2022-10-13  9:31 Marek Szuba
2022-10-04  0:53 Marek Szuba
2022-09-01 12:27 Marek Szuba
2022-08-31 14:01 Marek Szuba
2022-08-31 13:24 Marek Szuba
2022-08-31 13:17 Marek Szuba

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=1662034331.fa5f56620752ee67894da067c9d23c7ee460b316.marecki@gentoo \
    --to=marecki@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