From: Marius Bakke <mbakke@fastmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>, 29099@debbugs.gnu.org
Subject: [bug#29099] [PATCH] gnu: Add kodi-cli.
Date: Wed, 01 Nov 2017 22:32:34 +0100 [thread overview]
Message-ID: <87a8054rd9.fsf@fastmail.com> (raw)
In-Reply-To: <8760au8pfk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3347 bytes --]
Hello Oleg!
Oleg Pykhalov <go.wigust@gmail.com> writes:
> From 741284b1619490859910fb402802ab10b31f0fd2 Mon Sep 17 00:00:00 2001
> From: Oleg Pykhalov <go.wigust@gmail.com>
> Date: Wed, 1 Nov 2017 09:39:05 +0300
> Subject: [PATCH] gnu: Add kodi-cli.
>
> * gnu/packages/kodi.scm (kodi-cli): New variable.
Cool!
[...]
> +(define-public kodi-cli
> + (let ((commit "104dc23b2a993c8e6db8c46f4f8bec24b146549b") ; Add support for
> + (revision "1")) ; `$HOME/.kodirc'.
> + (package
> + (name "kodi-cli")
> + (version (string-append "1.1-" revision "." (string-take commit 7)))
> + (source (origin
> + (method git-fetch)
> + (uri (git-reference (url "https://github.com/nawar/kodi-cli")
> + (commit commit)))
> + (sha256
> + (base32
> + "1xjhasc5gngfxpr1dlzy6q24w0wpdfjx12p43fanjppxw4i49n5p"))
> + (file-name (string-append name "-" version "-checkout"))))
> + (build-system trivial-build-system)
> + (inputs `(("bash" ,bash)))
> + (propagated-inputs `(("curl" ,curl)))
There is only one reference to `curl` in the script, can you try to
substitute it with the absolute path and make it a regular input? It's
good to avoid propagation when we can.
> + (arguments
> + `(#:modules ((guix build utils))
> + #:builder
> + (begin
> + (use-modules (guix build utils))
> + (copy-recursively (assoc-ref %build-inputs "source") ".")
> + (substitute* "kodi-cli"
> + (("/bin/bash") (string-append (assoc-ref %build-inputs "bash")
> + "/bin/bash")))
> + (install-file "kodi-cli" (string-append %output "/bin")))))
(install-file ...) has an unspecified return value, so please return #t here.
> + (home-page "https://github.com/nawar/kodi-cli")
> + (synopsis "Bash script to send commands to Kodi using JSON RPC")
Maybe just "Control Kodi from the command line".
> + (description "@code{kodi-cli} provides the Bash script to send commands to
> +Kodi using JSON RPC.
Similarly, this sentence can be reduced to something like
"@code{kodi-cli} is a tool for sending commands to a Kodi server using
JSON-RPC.". Bash is an boring implementation detail IMO. :-)
> +
> +Feautures:
^ Stray 'u' character.
> +
> +@itemize
> +@item Play, pause, stop the current played video.
"currently playing"
> +@item Skip forward or backward in the current played video.
Same here. Maybe it should be "currently playing item", since I assume
this works for music as well.
> +@item Play or queue to the current list YouTube video.
"List of YouTube videos"?
> +@item Interactive and noninteractive volume control.
> +@item Interactive navigation.
> +@item Send text.
What does this mean? Arbitrary commands, or text notifications?
> +@item Toggle fullscreen.
> +@item Update or clean Kodi libraries.
> +@end itemize\n")
> + (license license:gpl2+))))
LGTM with some cosmetic improvements. And welcome!
By the way, if you use Kodi from Guix, feel free to update the 18
snapshot if you can. My media PC died a while back, and I didn't get a
replacement yet, so I have not been able to maintain the Kodi package.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-11-01 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 6:48 [bug#29099] [PATCH] gnu: Add kodi-cli Oleg Pykhalov
2017-11-01 21:32 ` Marius Bakke [this message]
2017-11-02 9:14 ` Oleg Pykhalov
2017-11-02 20:00 ` Marius Bakke
2017-11-03 3:57 ` Oleg Pykhalov
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=87a8054rd9.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=29099@debbugs.gnu.org \
--cc=go.wigust@gmail.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 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.