unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: picnoir@alternativebit.fr
Cc: 71064@debbugs.gnu.org
Subject: [bug#71064] [PATCH 7/7] gnu: services: nscd: add Nsncd optional support.
Date: Sun, 02 Jun 2024 20:55:54 +0200	[thread overview]
Message-ID: <87zfs3jhs5.fsf@gnu.org> (raw)
In-Reply-To: <cb8c3c48fb9affbab0a748be01f4afa743ad6ff2.1716121731.git.picnoir@alternativebit.fr> (picnoir@alternativebit.fr's message of "Sun, 19 May 2024 14:46:27 +0200")

Hi,

picnoir@alternativebit.fr skribis:

> From: Picnoir <picnoir@alternativebit.fr>
>
> * gnu/services/base.scm (services: nscd: add Nsncd optional support): Add a
> new nscd-use-nscd? field in the Nscd configuration record. When set to #t, the
> nscd service will use Nsncd in place of the Glibc's Nscd. I'm not 100% sure
> adding this to the existing Nscd service is a good idea, it's however the most
> convenient option for now. Or is it? :)

Well, there needs to be a flag somehow.  :-)

Nitpick: could you describe the changes at a syntactic level in the
commit log?  I know our conventions aren’t common today, so whoever
commits it can eventually tweak it on your behalf if needed.

> +  (use-nsncd?  nscd-use-nsncd?                     ;boolean
> +               (default #t))

I’m tempted to make it:

  (implementation nscd-implementation (default 'glibc))

And thus 'nsncd would be the other supported value.

Do you think that makes sense?

Anyhow, could you adjust doc/guix.texi to mention the new field?

Apart from that, the patch looks good to me.  Could you send an updated
version?

Thanks!

Ludo’.




  reply	other threads:[~2024-06-03  4:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19 12:34 [bug#71064] [PATCH 0/7] Nsncd: Introduce package + nscd service update picnoir
2024-05-19 12:46 ` [bug#71064] [PATCH 1/7] gnu: Add rust-libc-0.2.153 picnoir
2024-05-19 12:46 ` [bug#71064] [PATCH 2/7] gnu: Add rust-nix-0.28 picnoir
2024-05-19 12:46 ` [bug#71064] [PATCH 3/7] gnu: Add rust-dns-lookup-2 picnoir
2024-05-19 12:46 ` [bug#71064] [PATCH 4/7] gnu: Add rust-temp-env-0.3 picnoir
2024-05-19 12:46 ` [bug#71064] [PATCH 5/7] gnu: Add rust-slog-async-2-8 picnoir
2024-05-19 12:46 ` [bug#71064] [PATCH 6/7] gnu: Add nsncd picnoir
2024-05-19 12:46 ` [bug#71064] [PATCH 7/7] gnu: services: nscd: add Nsncd optional support picnoir
2024-06-02 18:55   ` Ludovic Courtès [this message]
2024-06-02 18:52 ` [bug#71064] [PATCH 0/7] Nsncd: Introduce package + nscd service update 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zfs3jhs5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=71064@debbugs.gnu.org \
    --cc=picnoir@alternativebit.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).