GNU bug report logs -
#61587
[PATCH 0/8] networking services refactoring
Previous Next
Reported by: Bruno Victal <mirai <at> makinata.eu>
Date: Fri, 17 Feb 2023 21:14:02 UTC
Severity: normal
Tags: patch
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Hi,
Bruno Victal <mirai <at> makinata.eu> skribis:
> Note: This also makes wpa-supplicant an optional requirement.
>
> * gnu/services/networking.scm (<network-manager-configuration>)
> [shepherd-requirement]: New field.
> (network-manager-shepherd-service): Honor it.
> (network-manager-configuration-shepherd-requirement): Export accessor.
> * doc/guix.texi (Networking Setup): Document it.
[...]
> +@item @code{shepherd-requirement} (default: @code{()})
> +This option can be used to provide a list of symbols naming Shepherd services
> +that this service will depend on, such as @code{'wpa-supplicant} or
> +@code{'iwd} if you require authenticated access for encrypted WiFi or Ethernet
> +networks.
For clarity, I’d write the list: @code{'(wpa-supplicant)}.
> + (shepherd-requirement network-manager-configuration-shepherd-requirement
> + (default '()))
[...]
> - (requirement (append '(user-processes dbus-system loopback)
> - (if iwd? '(iwd) '(wpa-supplicant))))
> + (requirement `(user-processes dbus-system loopback
> + ,@shepherd-requirement
> + ,@(if iwd? '(iwd) '())))
To preserve backward compatibility and to provide a reasonable default
(with working WiFi), I think the default for ‘shepherd-requirement’
should be '(wpa-supplicant) rather than the empty list.
(BTW, it seems that wpa-supplicant can be DBus-activated, maybe that’s
what we should do instead? But let’s forget about it for this patch
series.)
Thanks,
Ludo’.
This bug report was last modified 2 years and 76 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.