unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 53222@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#53222] [PATCH] gnu: autokey fix paths.
Date: Fri, 14 Jan 2022 23:35:18 +0100	[thread overview]
Message-ID: <7459eb594a85d02eb744c9bd5b83941576990aab.camel@telenet.be> (raw)
In-Reply-To: <brciF3ZHBesTmBnzZFGJl4gnkN6lwWQv8AtBxXWSoI4Qi4Cs4b6d8QI93TIUM7O8SKQ9i2hx4rP3ly9GKF35uiHA3AujZCxl3CrujK1UmlI=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

John Kehayias schreef op vr 14-01-2022 om 20:40 [+0000]:
> -          (add-after 'install 'wrap-autokey
> +                 (string-append "\"" (search-input-file inputs
> "bin/zenity") "\"")))
> +              (substitute* "autokey-shell"
> +                (("'ipython3'")
> +                 (string-append "'" (which "ipython3") "'"))
> +                (("'python3'")
> +                 (string-append "'" (which "python3") "'")))))

Wouldn't these also need to use use 'search-input-file'?
I think I've mentioned before why 'search-input-file' needs to be
used in these kind of contexts instead of 'which' (something with
cross-compilation), if not I can explain.

> [in propagated inputs]
> +           python-ipython
> +           wmctrl
> +           zenity

Do we need propagation here?  I don't quite see the need here
and propagation can cause trouble like profile conflcts during
partial upgrades (i.e. "guix install foo" after "guix pull"
without "guix package -u")

FWIW autokey is never used as library (except for autokey scripts
but I assume autokey scripts are interpreted in the same process
as autokey?) and wrap-program sets GUIX_PYTHONPATH so I think all
python libraries here could be depropagated?  Though that might
be getting out of scope of the original patch, so only if you want
to investigate.

Othderwise, the patch you attached LGTM.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-01-14 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 21:03 [bug#53222] [PATCH] gnu: Add autokey John Kehayias via Guix-patches via
2022-01-12 21:22 ` Nicolas Goaziou
2022-01-12 21:26 ` Maxime Devos
2022-01-12 21:55   ` John Kehayias via Guix-patches via
2022-01-13  7:34     ` Maxime Devos
2022-01-14 20:40 ` [bug#53222] [PATCH] gnu: autokey fix paths John Kehayias via Guix-patches via
2022-01-14 22:35   ` Maxime Devos [this message]
2022-01-14 22:48     ` John Kehayias via Guix-patches via
2022-01-15 11:17       ` Maxime Devos
2022-01-15 20:03         ` John Kehayias via Guix-patches via
2022-01-15 20:32           ` bug#53222: " Nicolas Goaziou

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=7459eb594a85d02eb744c9bd5b83941576990aab.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53222@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=mail@nicolasgoaziou.fr \
    /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).