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: net-libs/libsearpc/
Date: Mon, 11 Mar 2024 14:24:09 +0000 (UTC)	[thread overview]
Message-ID: <1710166968.86f1f76c68a4d8aaf3246038f64fc66f36cd7129.sam@gentoo> (raw)

commit:     86f1f76c68a4d8aaf3246038f64fc66f36cd7129
Author:     Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Mon Mar 11 01:33:33 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Mar 11 14:22:48 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86f1f76c

net-libs/libsearpc: remove useless dependency on simplejson

This module is effectively just the stdlib "json" module, but in very
very old versions of python it was not yet in the stdlib. As in, older
than python 2.6.

Since 2014, libsearpc hasn't actually used simplejson at all, just the
stdlib:
https://github.com/haiwen/libsearpc/commit/80b73555924bc780b69da8b5974338fff1441829

Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../{libsearpc-3.3.0-r1.ebuild => libsearpc-3.3.0-r2.ebuild}       | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/net-libs/libsearpc/libsearpc-3.3.0-r1.ebuild b/net-libs/libsearpc/libsearpc-3.3.0-r2.ebuild
similarity index 88%
rename from net-libs/libsearpc/libsearpc-3.3.0-r1.ebuild
rename to net-libs/libsearpc/libsearpc-3.3.0-r2.ebuild
index 9df86b3f3be3..799b52ac7a0b 100644
--- a/net-libs/libsearpc/libsearpc-3.3.0-r1.ebuild
+++ b/net-libs/libsearpc/libsearpc-3.3.0-r2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -22,10 +22,7 @@ REQUIRED_USE="${PYTHON_REQUIRED_USE}"
 DEPEND="${PYTHON_DEPS}
 	>=dev-libs/glib-2.26.0
 	>=dev-libs/jansson-2.2.1:="
-RDEPEND="${DEPEND}
-	$(python_gen_cond_dep '
-		dev-python/simplejson[${PYTHON_USEDEP}]
-	')"
+RDEPEND="${DEPEND}"
 
 S="${WORKDIR}/${PN}-${RELEASE_COMMIT}"
 


             reply	other threads:[~2024-03-11 14:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 14:24 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-10 18:03 [gentoo-commits] repo/gentoo:master commit in: net-libs/libsearpc/ Sam James
2024-07-30 19:01 Pacho Ramos
2024-07-30 19:01 Pacho Ramos
2023-12-04  9:25 Viorel Munteanu
2023-03-05  7:33 Joonas Niilola
2022-11-23 17:55 Joonas Niilola
2022-09-01  6:27 Joonas Niilola
2022-04-07 20:58 Jakov Smolić
2021-10-26  6:52 Arthur Zamarin
2021-09-25 19:08 Sam James
2021-08-04 14:46 David Seifert
2021-07-26 22:01 Conrad Kostecki
2020-10-06  8:15 Joonas Niilola
2020-10-06  8:15 Joonas Niilola
2020-09-29 10:26 Joonas Niilola
2020-09-19 11:28 Michał Górny
2020-08-02 12:03 Michał Górny
2019-12-18 16:32 Joonas Niilola
2019-12-18 16:32 Joonas Niilola
2019-07-01  1:24 Jonas Stein
2018-04-13 18:26 Michał Górny
2018-04-13 18:26 Michał Górny
2017-11-15 22:13 Patrice Clement
2017-04-14 20:30 Patrice Clement
2017-04-14 20:30 Patrice Clement
2017-04-13 21:20 Patrice Clement

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=1710166968.86f1f76c68a4d8aaf3246038f64fc66f36cd7129.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