From: "Ludovic Courtès" <ludo@gnu.org>
To: Lars Bilke <lars.bilke@ufz.de>
Cc: 74667@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#74667] [PATCH] doc: Add note on nsncd as a replacement for nscd.
Date: Thu, 12 Dec 2024 23:08:21 +0100 [thread overview]
Message-ID: <87bjxg5zca.fsf@gnu.org> (raw)
In-Reply-To: <15fbddff7e92d9e2acd24842da09dbbab66a566f.1733223713.git.lars.bilke@ufz.de> (Lars Bilke's message of "Tue, 03 Dec 2024 12:01:53 +0100")
Hi Lars,
Lars Bilke <lars.bilke@ufz.de> skribis:
> * doc/guix.texi Add note on nsncd in Name Service Switch section.
>
> Change-Id: Ib804ab2e7d83d13f8f81d875f957eae2304eb232
[...]
> +Please note that
> +@uref{https://gitlab.archlinux.org/archlinux/packaging/packages/glibc/-/commit/25032a8abb2760257c3dceb78e649a0a2c4e3ab2, glibc @geq{} 2.38-4}
> +does not provide @command{nscd} anymore. @command{nsncd} can be used as
To be precise, it’s only the ‘glibc’ package of Arch that doesn’t
provide ‘nscd’; upstream 2.39 (which we use) provides it.
So I would suggest: “Note that @command{nscd} is no longer provided on
some GNU/Linux distros, such as Arch Linux (as of Dec. 2024).”
Am I right?
Nitpick: please leave two spaces after end-of-sentence periods (this is
conventional).
> +a drop-in-replacement. See @uref{https://github.com/twosigma/nsncd, nsncd on GitHub}
> +and @uref{https://flokli.de/posts/2022-11-18-nsncd/, this blog post} for
> +more information.
s/nsncd on GitHub/the nsncd repository/
Could you send an updated patch?
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-12-12 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 11:01 [bug#74667] [PATCH] doc: Add note on nsncd as a replacement for nscd Lars Bilke
2024-12-12 22:08 ` Ludovic Courtès [this message]
2024-12-18 9:51 ` [bug#74667] [PATCH v2] " Lars Bilke
2024-12-18 11:10 ` bug#74667: " Ludovic Courtès
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=87bjxg5zca.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74667@debbugs.gnu.org \
--cc=lars.bilke@ufz.de \
--cc=maxim.cournoyer@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.