From: Skyler Ferris via Guix-patches via <guix-patches@gnu.org>
To: Ian Eure <ian@retrospec.tv>, 69692@debbugs.gnu.org
Subject: [bug#69692] [PATCH] gnu: Add home-jellyfin-mpv-shim-service-type.
Date: Mon, 18 Mar 2024 22:14:08 +0000 [thread overview]
Message-ID: <8c8f0aee-f099-46ad-91f0-89e7b1dd789d@protonmail.com> (raw)
In-Reply-To: <7d396f735f82369731c90195c7b8e7dc0fcf9acd.1710048182.git.ian@retrospec.tv>
[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]
Hi Ian,
I don't have the setup required to try running this service but 2 things stand out to me when reading through it.
On 3/9/24 21:24, Ian Eure wrote:
> +To enable, add this to your home services:
> +
> +@lisp
> +(service home-jellyfin-mpv-shim-service-type #f)
> +@end lisp
You can add a default-value field to the service definition like so:
(define-public home-jellyfin-mpv-shim-service-type
(service-type
(name 'home-jellyfin-mpv-shim)
(default-value #f)
(extensions (list (service-extension home-shepherd-service-type
jellyfin-mpv-shim-shepherd-service)
;; Ensure 'home-x11-service-type' is instantiated so we
;; can depend on the Shepherd 'x11-display' service.
(service-extension home-x11-service-type
(const #t))))
(description "Run Jellyfin MPV Shim.")))
Then, users can simply use (service home-jellyfish-mpv-shim-service-type) without having to specify #f manually And if the service ever changes in the future and this value becomes useful then you can provide a reasonable default without requiring users to change their code. (https://guix.gnu.org/manual/en/html_node/Service-Reference.html)
> +
> +The service only starts if @code{jellyfin-mpv-shim} has been configured with a remote server and credentials. This must be done manually, by launching @code{jellyfin-mpv-shim}. After configuring the server, the service will start automatically when you log in.
Would it make sense to launch this program automatically if it is not configured? Presumably if someone adds the service then they want to configure a server. The value passed to the service could be used to specify whether or not the program should automatically launch so that users who do not want this behavior can disable it (note that if you decide to implement this then the configuration value should be an instance of a new structure defined to store configuration for this service, not a simple boolean; again, this makes things easier in the future so that if you want to add more fields pre-existing code will still work).
Regards,
Skyler
[-- Attachment #2: Type: text/html, Size: 3136 bytes --]
next prev parent reply other threads:[~2024-03-18 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 5:24 [bug#69692] [PATCH] gnu: Add home-jellyfin-mpv-shim-service-type Ian Eure
2024-03-18 22:14 ` Skyler Ferris via Guix-patches via [this message]
2024-05-16 1:27 ` Ian Eure
2024-08-22 14:57 ` Ian Eure
2024-09-08 23:10 ` [bug#69692] [PATCH v2 0/1] " Ian Eure
2024-09-08 23:10 ` [bug#69692] [PATCH v2 1/1] " Ian Eure
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=8c8f0aee-f099-46ad-91f0-89e7b1dd789d@protonmail.com \
--to=guix-patches@gnu.org \
--cc=69692@debbugs.gnu.org \
--cc=ian@retrospec.tv \
--cc=skyvine@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).