From: John Darrington <john@darrington.wattle.id.au>
To: Ludovic Court??s <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add Kerberos client service.
Date: Wed, 30 Nov 2016 14:44:18 +0100 [thread overview]
Message-ID: <20161130134418.GA21749@jocasta.intra> (raw)
In-Reply-To: <874m2pktc2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2682 bytes --]
On Wed, Nov 30, 2016 at 02:09:17PM +0100, Ludovic Court??s wrote:
John Darrington <jmd@gnu.org> skribis:
> * doc/guix.texi (Kerberos Services)[Krb5 Service]: New subsubheading.
> * gnu/services/kerberos.scm (krb5-service-type): New variable.
Please mention the configuration.scm changes.
ok.
> +@subsubheading Krb5 Service
> +
> +The krb5 service provides the configuration for Kerberos clients, using
> +the MIT implementation of the Kerberos protocol version@tie{}5.
Please take into account my previous suggestions:
https://lists.gnu.org/archive/html/guix-devel/2016-11/msg00922.html
ok
Shouldn???t it be a single comma in @uref?
I don't think so. The Texinfo manual suggests, that in this case, the second arg
should be empty.
> (define (validate-configuration config fields)
> (for-each (lambda (field)
> (let ((val ((configuration-field-getter field) config)))
> - (unless ((configuration-field-predicate field) val)
> + (unless (or (not val) ((configuration-field-predicate field) val))
> (configuration-field-error
> (configuration-field-name field) val))))
Here you???re assuming that when VAL is #f, it???s necessary invalid, an
assumption that???s questionable and wasn???t made until now.
No. I'm assuming the exact opposite, namely, that #f is a *valid* value.
Can you instead change your own field predicate to do that?
I could do that, but then I'd be defining a lot of them which are substantially
identical to existing ones - and below, you say that you don't want me to
duplicate code ...
> +
> +(define (serialize-non-negative-integer field-name val)
> + (if val
> + (serialize-field* field-name val)))
> +
> +(define (serialize-integer field-name val)
> + (if val
> + (serialize-field* field-name val))
No ???else??? here? Looks like a bug.
No. The idea is, that if fields are #f then they output absolutely nothing.
How much of this is copied from configuration.scm? I don???t want
duplicated code here.
Much of it was copied, but modified where appropriate. None is identical
I don't think.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-11-30 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 19:58 [PATCH] gnu: Add kerberos service John Darrington
2016-11-18 15:23 ` John Darrington
2016-11-18 22:51 ` Ludovic Courtès
2016-11-19 6:57 ` John Darrington
2016-11-21 8:59 ` Ludovic Courtès
2016-11-22 17:52 ` [PATCH] gnu: Add Kerberos client service John Darrington
2016-11-23 22:01 ` Ludovic Courtès
2016-11-29 18:39 ` John Darrington
2016-11-29 18:39 ` John Darrington
2016-11-30 13:09 ` Ludovic Courtès
2016-11-30 13:44 ` John Darrington [this message]
2016-11-30 13:52 ` Andy Wingo
2016-12-03 12:27 ` John Darrington
2016-12-03 15:13 ` 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=20161130134418.GA21749@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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).