From: Maxime Devos <maximedevos@telenet.be>
To: Maya <maya.omase@protonmail.com>
Cc: "56797@debbugs.gnu.org" <56797@debbugs.gnu.org>
Subject: [bug#56797] [PATCH] gnu: services: fprintd: Add PAM configuration.
Date: Wed, 27 Jul 2022 23:56:24 +0200 [thread overview]
Message-ID: <946b358e-da78-9307-ff12-8a4a060867a8@telenet.be> (raw)
In-Reply-To: <LcTuwD5B16pAYt1fDmGz1h8p7LuuJXmaMo9xaUF24goWjOD_OG4KHOhDM59KlDwoDRXpCnsHaUW8j49fWudFgjA7_XN-Dm1w2OO5gsblHN0=@protonmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1961 bytes --]
On 27-07-2022 22:26, Maya wrote:
>> Documentation is missing (in the manual), so as-is, this new feature is
>> hard to find.
> Oh? I didn't know that. Doesn't define-configuration generate documentation automatically? If it does not, I will hapilly add it, but I have never written any, so it will be a learning process.
>
There is some procedure that takes a record type and generates some
documentation, but it is not automatically copied into the manual, you
will have to do that yourself (and maybe tweak the result a little:
what's a good docstring in code doesn't always fit very well in a manual).
>> Also, the manual required giving every top-level procedure a docstring
>> IIRC,
> There is that requirement, yes. But there weren't any around this method so I thought the configuration sufficed, but if it is a requirement, I will do that.
>
I don't know if the requirement is overly strictly formulated or if the
surrounding code is wrong.
>> This documentation is unclear -- does this field need to be set to the
>> _name_ of the module, or to the_file name_ of the_shared library_ (as
>> a file-like, not a direct file name, because of staging), or ...? Also,
>> the 'list' check can be more precise, IIRC there was some method for not
>> just using list? but doing things like list-of-strings?.
> The name of the pam module, not a shared library. So the file in /etc/pam.d. It is a direct name, since it is not inside the store, pam modules have static path.
To be clear, it is clear if you look at the default value, but I think
it's best to be explicit in the documentation.
> As for the configuration options, it's my first time using them and I didn't really understand the define-syntax definition, so I really just skimmed through the guix repository for some uses.
IIRC, there are some procedures you can use to define list-of-x?
procedures but I don't recall the details.
Greetings,
Maxime.
[-- Attachment #1.1.1.2: Type: text/html, Size: 3484 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-27 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:57 [bug#56797] [PATCH] gnu: services: fprintd: Add PAM configuration Maya via Guix-patches via
2022-07-27 16:04 ` Maxime Devos
2022-07-27 16:06 ` Maxime Devos
2022-07-27 16:12 ` Maxime Devos
2022-07-27 20:26 ` Maya via Guix-patches via
2022-07-27 21:56 ` Maxime Devos [this message]
2022-08-09 15:00 ` 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=946b358e-da78-9307-ff12-8a4a060867a8@telenet.be \
--to=maximedevos@telenet.be \
--cc=56797@debbugs.gnu.org \
--cc=maya.omase@protonmail.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 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).