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-libs/yaz/
Date: Fri, 18 Jul 2025 15:18:21 +0000 (UTC)	[thread overview]
Message-ID: <1752851883.2bbb9565fb3fba6d5294b279e063538cb6b57b02.sam@gentoo> (raw)

commit:     2bbb9565fb3fba6d5294b279e063538cb6b57b02
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 18 14:58:33 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jul 18 15:18:03 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2bbb9565

dev-libs/yaz: allow use of dev-libs/libmemcached-awesome

dev-libs/libmemcached-awesome is an API & ABI compatible fork of
dev-libs/libmemcached. The latter hasn't had updates or fixes in quite
some time.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/yaz/{yaz-5.35.1.ebuild => yaz-5.35.1-r1.ebuild} | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/dev-libs/yaz/yaz-5.35.1.ebuild b/dev-libs/yaz/yaz-5.35.1-r1.ebuild
similarity index 94%
rename from dev-libs/yaz/yaz-5.35.1.ebuild
rename to dev-libs/yaz/yaz-5.35.1-r1.ebuild
index ecb361a1f76d..f8d1f673320b 100644
--- a/dev-libs/yaz/yaz-5.35.1.ebuild
+++ b/dev-libs/yaz/yaz-5.35.1-r1.ebuild
@@ -27,7 +27,12 @@ RDEPEND="
 	net-libs/gnutls:=
 	sys-libs/readline:=
 	virtual/libintl
-	memcached? ( dev-libs/libmemcached )
+	memcached? (
+		|| (
+			dev-libs/libmemcached-awesome
+			dev-libs/libmemcached
+		)
+	)
 	redis? ( dev-libs/hiredis:= )
 	tcpd? ( sys-apps/tcp-wrappers )
 "


             reply	other threads:[~2025-07-18 15:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 15:18 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18  1:53 [gentoo-commits] repo/gentoo:master commit in: dev-libs/yaz/ Sam James
2025-08-18  1:53 Sam James
2025-07-04 20:38 Sam James
2025-04-26  1:17 Sam James
2025-04-26  1:17 Sam James
2025-04-26  0:39 Sam James
2025-04-26  0:32 Sam James
2025-03-08  7:20 Arthur Zamarin
2025-03-08  7:20 Arthur Zamarin
2025-01-02  0:14 Conrad Kostecki
2024-10-31 23:32 Andreas K. Hüttel
2024-08-25 15:24 Andreas K. Hüttel
2024-02-17 14:48 Sam James
2024-02-14 19:47 Arthur Zamarin
2024-02-14 19:42 Sam James
2024-02-14 16:48 Sam James
2024-01-30  6:58 Sam James
2022-12-18 20:07 Arthur Zamarin
2022-12-18 12:28 Sam James
2022-12-18 11:55 Sam James
2022-12-18 11:34 Sam James
2022-11-24 18:14 Conrad Kostecki
2022-08-26 12:04 Sam James
2022-06-12  7:33 Joonas Niilola
2022-02-19 12:38 Arthur Zamarin
2022-02-19 10:34 Arthur Zamarin
2021-08-16  3:15 Sam James
2021-08-16  3:15 Sam James
2021-08-16  2:43 Sam James
2021-07-25 21:46 Andreas K. Hüttel
2020-02-18 20:06 Andreas Sturmlechner
2016-11-05 17:21 Pacho Ramos
2016-11-05 17:16 Pacho Ramos
2016-10-01 14:12 Jeroen Roovers
2016-08-30 20:29 Markus Meier
2016-07-04 11:36 Tobias Klausmann
2016-07-03 18:45 Andreas Hüttel
2016-06-28  6:00 Michał Górny
2016-06-26 12:21 Anthony G. Basile

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=1752851883.2bbb9565fb3fba6d5294b279e063538cb6b57b02.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