From: Juliana Sims via Guix-patches via <guix-patches@gnu.org>
To: neox@gnu.org
Cc: Juliana Sims <juli@incana.org>, 70845@debbugs.gnu.org
Subject: [bug#70845] [PATCH v2] services: Add fancontrol-service-type.
Date: Wed, 15 May 2024 18:16:25 -0400 [thread overview]
Message-ID: <DJSJDS.VLIJN2A399JX2@incana.org> (raw)
In-Reply-To: <20240509154032.5047-1-neox@gnu.org>
Hi Adrien,
Thanks for this patch! It looks pretty good, though I do have a few
small bits of feedback.
First and foremost, this service needs documentation. Could you add
that as well? Speaking of documentation, the 'documentation' field of
your Shepherd service has an extraneous bit of whitespace.
Is it absolutely vital to use root for this service? Could you instead
create a user and usergroup with only the privileges required to run
fancontrol? You may need to do something with udev so that works. I'm
not sure exactly what privileges are required, but avoiding root seems
like a good idea.
That's the only real critique I have here. Consider the rest of this
email fun ideas rather than review per se :)
We had an out-of-band exchange about this patch that I'll summarize
here for the record. I echoed the sentiments of the reviewer who
suggested exposing the fancontrol package so that users could change
it. Your response was that the configuration is generated by pwmconfig
and therefore it wouldn't make sense to provide a Scheme interface to
configuration.
I don't know this package or how it works, but would it be possible for
this service to generate that config automatically when it's first
started? If the config is customizable about generation, you could then
expose various settings through the Guix service interface for users to
modify and rewrite the file for them. That would make using
define-configuration worthwhile for more than simply the ability to
change the package.
All that aside, you should be able to expose the package setting to
users without using define-configuration.
Best,
Juli
next prev parent reply other threads:[~2024-05-15 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 15:37 [bug#70845] [PATCH] services: Add fancontrol-service-type Adrien 'neox' Bourmault
2024-05-09 17:39 ` Denis 'GNUtoo' Carikli
2024-05-09 19:28 ` Adrien 'neox' Bourmault via Guix-patches via
2024-05-09 19:30 ` Adrien 'neox' Bourmault
2024-05-12 15:17 ` Denis 'GNUtoo' Carikli
2024-05-13 14:06 ` [bug#70845] [PATCH v2] " Adrien 'neox' Bourmault
2024-05-15 22:16 ` Juliana Sims via Guix-patches via [this message]
2024-05-16 9:27 ` Adrien 'neox' Bourmault
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=DJSJDS.VLIJN2A399JX2@incana.org \
--to=guix-patches@gnu.org \
--cc=70845@debbugs.gnu.org \
--cc=b8ea66dd0b5edd9e8d345a0beda3198049ab6231.1715609187.git.neox@gnu.org \
--cc=juli@incana.org \
--cc=neox@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 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.