From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53222@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#53222] [PATCH] gnu: autokey fix paths.
Date: Fri, 14 Jan 2022 20:40:11 +0000 [thread overview]
Message-ID: <brciF3ZHBesTmBnzZFGJl4gnkN6lwWQv8AtBxXWSoI4Qi4Cs4b6d8QI93TIUM7O8SKQ9i2hx4rP3ly9GKF35uiHA3AujZCxl3CrujK1UmlI=@protonmail.com> (raw)
In-Reply-To: <Kubuvj_ZYaawCDW6qu7U-Z-q_Sj1s_8I8hNmJo1u-hkGHByPRsJ_y6joxVtJiJnezoX01VMS1538BIBPlkhDKYxnu0uwEA3nZzb_YRDbszE=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
Hi Maxime,
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, January 13th, 2022 at 2:34 AM, Maxime Devos wrote:
>> I can submit a patch to change the wrap and inputs if that would be cleaner.
>
> * Maybe you make the GUIX_PYTHONPATH wrapping explicit (e.g. by
> removing the wrap phase, or moving the 'wrap-autokey' phase before
> the 'wrap', or letting it replace the 'wrap' phase), adding a comment
>
> ;; Use 'prefix' instead of '=' to allow the user to use additional
> ;; Python libraries from their autokey scripts.
> * or maybe don't do that, but still add a similar comment to the 'wrap'
> phase.
> * Could you make the comment next to #:tests? a bit more explicit?
>
Okay, I hope I understood correctly, attached is a patch with these updates (on top of the already applied originally package addition).
I noticed that autokey-shell had calls to ipython3 (or python3) that should have been substituted, so I did that with the added input for ipython3.
Added the comment about the tests and GI_TYPELIB_PATH. Note that this is there because otherwise the gtk pieces won't run as it needs the girepository (I think this is also the reason this is done in most cases?). I did add the comment you suggested so it is clear this is prefix in case there are other GI paths a user wants, and that the GUIX_PYTHONPATH wrapping is done by python-build-system already.
Thanks again!
John
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-autokey-Fix-paths.patch --]
[-- Type: text/x-patch; name=0001-gnu-autokey-Fix-paths.patch, Size: 2832 bytes --]
From aec4732cac7e239590c7bb85649fd99f6be2d475 Mon Sep 17 00:00:00 2001
From: John Kehayias <john.kehayias@protonmail.com>
Date: Fri, 14 Jan 2022 15:26:36 -0500
Subject: [PATCH] gnu: autokey: Fix paths.
* gnu/packages/python-xyz.scm (autokey): Add comments on the disabled tests
and GI_TYPELIB_PATH wrapping.
[inputs]: Add ipython.
[phases]{fix-paths}: Use paths to ipython3 and python3 in autokey-shell
script.
{wrap-autokey}: Change name to...
{wrap-autokey-gi}: ...this and move to before wrap for clarity.
---
gnu/packages/python-xyz.scm | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index b85232f2b7..7ec671a476 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -4197,7 +4197,9 @@ (define-public autokey
(build-system python-build-system)
(arguments
(list
- #:tests? #f ; Tests are deprecated/broken until next version.
+ ;; Tests are deprecated and broken until next version, see
+ ;; https://github.com/autokey/autokey/issues/327
+ #:tests? #f
#:phases
#~(modify-phases %standard-phases
(add-after 'unpack 'fix-paths
@@ -4206,8 +4208,16 @@ (define-public autokey
(("\"wmctrl\"")
(string-append "\"" (search-input-file inputs "bin/wmctrl") "\""))
(("\"zenity\"")
- (string-append "\"" (search-input-file inputs "bin/zenity") "\"")))))
- (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") "'")))))
+ ;; Use 'prefix' instead of '=' to allow the user to use additional
+ ;; GI paths from their autokey scripts. GUIX_PYTHONPATH is already
+ ;; wrapped with prefix in python-build-system's wrap.
+ (add-before 'wrap 'wrap-autokey-gi
(lambda _
(let ((gi-typelib-path (getenv "GI_TYPELIB_PATH")))
(for-each
@@ -4223,14 +4233,14 @@ (define-public autokey
gtksourceview-3
libappindicator
libnotify
- wmctrl
- zenity))
- (propagated-inputs
- (list python-dbus
+ python-dbus
+ python-ipython
python-pygobject
python-pyinotify
python-pyqt+qscintilla
- python-xlib))
+ python-xlib
+ wmctrl
+ zenity))
(home-page "https://github.com/autokey/autokey")
(synopsis
"Keyboard and GUI automation utility")
--
2.34.0
next prev parent reply other threads:[~2022-01-14 20:45 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 ` John Kehayias via Guix-patches via [this message]
2022-01-14 22:35 ` [bug#53222] [PATCH] gnu: autokey fix paths Maxime Devos
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='brciF3ZHBesTmBnzZFGJl4gnkN6lwWQv8AtBxXWSoI4Qi4Cs4b6d8QI93TIUM7O8SKQ9i2hx4rP3ly9GKF35uiHA3AujZCxl3CrujK1UmlI=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=53222@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=mail@nicolasgoaziou.fr \
--cc=maximedevos@telenet.be \
/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).