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] repo/gentoo:master commit in: dev-util/gef/
Date: Mon, 31 Jan 2022 03:54:06 +0000 (UTC)	[thread overview]
Message-ID: <1643600954.d4a18ac6d209a8fad9ece954c9da75f5c97434e0.sam@gentoo> (raw)

commit:     d4a18ac6d209a8fad9ece954c9da75f5c97434e0
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 31 03:49:14 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan 31 03:49:14 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d4a18ac6

dev-util/gef: strip pylint dependency

We don't want this even for running test suites usually as it's
not helpful/indicative downstream of whether something is
working properly.

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

 dev-util/gef/{gef-2021.10.ebuild => gef-2021.10-r1.ebuild} | 6 ++++++
 dev-util/gef/gef-9999.ebuild                               | 6 ++++++
 2 files changed, 12 insertions(+)

diff --git a/dev-util/gef/gef-2021.10.ebuild b/dev-util/gef/gef-2021.10-r1.ebuild
similarity index 93%
rename from dev-util/gef/gef-2021.10.ebuild
rename to dev-util/gef/gef-2021.10-r1.ebuild
index 0d0db6c0ae2b..1591c4b14506 100644
--- a/dev-util/gef/gef-2021.10.ebuild
+++ b/dev-util/gef/gef-2021.10-r1.ebuild
@@ -44,6 +44,12 @@ BDEPEND="doc? ( dev-python/mkdocs )
 		')
 	)"
 
+python_prepare_all() {
+	sed -i -e '/pylint/d' requirements.txt || die
+
+	distutils-r1_python_prepare_all
+}
+
 src_compile() {
 	# Tries to compile tests
 	:

diff --git a/dev-util/gef/gef-9999.ebuild b/dev-util/gef/gef-9999.ebuild
index 0d0db6c0ae2b..1591c4b14506 100644
--- a/dev-util/gef/gef-9999.ebuild
+++ b/dev-util/gef/gef-9999.ebuild
@@ -44,6 +44,12 @@ BDEPEND="doc? ( dev-python/mkdocs )
 		')
 	)"
 
+python_prepare_all() {
+	sed -i -e '/pylint/d' requirements.txt || die
+
+	distutils-r1_python_prepare_all
+}
+
 src_compile() {
 	# Tries to compile tests
 	:


             reply	other threads:[~2022-01-31  3:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31  3:54 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-14  4:57 [gentoo-commits] repo/gentoo:master commit in: dev-util/gef/ Sam James
2024-01-14  4:53 Sam James
2024-01-14  4:53 Sam James
2024-01-14  4:53 Sam James
2024-01-14  4:53 Sam James
2023-10-04 21:56 Conrad Kostecki
2023-09-26 18:25 Sam James
2023-09-26 17:58 Sam James
2023-08-26  4:01 Sam James
2023-08-26  4:01 Sam James
2023-08-26  4:01 Sam James
2023-05-25  8:25 Arthur Zamarin
2023-05-25  8:12 Arthur Zamarin
2023-04-25  1:57 Sam James
2023-04-25  1:57 Sam James
2023-04-14 19:43 Sam James
2023-04-14  4:04 Sam James
2023-02-25  5:47 Arthur Zamarin
2023-01-14 10:00 Arthur Zamarin
2023-01-10  4:13 Sam James
2023-01-05 16:42 Arthur Zamarin
2023-01-05 16:42 Arthur Zamarin
2022-10-30  9:35 Sam James
2022-10-30  9:35 Sam James
2022-07-26  4:26 Sam James
2022-06-28  9:31 Sam James
2022-01-31  3:55 Sam James
2022-01-31  3:54 Sam James
2022-01-28  8:22 Sam James
2022-01-28  5:18 Sam James
2022-01-28  5:18 Sam James

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=1643600954.d4a18ac6d209a8fad9ece954c9da75f5c97434e0.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