From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Hilton Chain" <hako@ultrarare.space>, <56717@debbugs.gnu.org>
Subject: [bug#56717] [PATCH 2/2] gnu: Add python-autotiling.
Date: Sat, 23 Jul 2022 09:54:57 +0100 [thread overview]
Message-ID: <CLMWR6CZTJC4.3BY34EAKG35QU@guix-aspire> (raw)
In-Reply-To: <d98d8429224b48f25db0ca9ba4419f30fd226dc4.1658559627.git.hako@ultrarare.space>
On Sat Jul 23, 2022 at 7:33 AM BST, Hilton Chain via Guix-patches via wrote:
> +(define-public python-autotiling
I think this should be changed to `i3-autotiling`, since it's a Python
program, not a library.
> + (package
> + (name "autotiling")
Same here.
> + (arguments
> + '(#:tests? #f))
Can you add an explanation and change to (list ...) style here too,
please?
> + (inputs (list python-wheel python-xlib))
I think python-wheel only needs to be a native-input, and python-xlib
can be removed if you propagate it in python-i3ipc.
-- (
next prev parent reply other threads:[~2022-07-23 8:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 13:08 [bug#56717] [PATCH v4 0/2] gnu: Add python-i3ipc and i3-autotiling Hilton Chain via Guix-patches via
2022-07-23 12:49 ` [bug#56717] [PATCH v3 " Hilton Chain via Guix-patches via
2022-07-23 10:40 ` [bug#56717] [PATCH v2 " Hilton Chain via Guix-patches via
2022-07-23 7:00 ` [bug#56717] [PATCH 0/2] gnu: Add python-i3ipc and python-autotiling Hilton Chain via Guix-patches via
2022-07-23 6:31 ` [bug#56717] [PATCH 1/2] gnu: Add python-i3ipc Hilton Chain via Guix-patches via
2022-07-23 8:50 ` ( via Guix-patches via
2022-07-23 8:54 ` ( via Guix-patches via
2022-07-23 6:33 ` [bug#56717] [PATCH 2/2] gnu: Add python-autotiling Hilton Chain via Guix-patches via
2022-07-23 8:54 ` ( via Guix-patches via [this message]
2022-07-23 10:31 ` [bug#56717] [PATCH v2 1/2] gnu: Add python-i3ipc Hilton Chain via Guix-patches via
2022-07-23 10:31 ` [bug#56717] [PATCH v2 2/2] gnu: Add i3-autotiling Hilton Chain via Guix-patches via
2022-07-23 10:52 ` ( via Guix-patches via
2022-07-23 11:01 ` Maxime Devos
2022-07-23 11:38 ` Hilton Chain via Guix-patches via
2022-07-23 12:17 ` Maxime Devos
2022-07-23 12:22 ` ( via Guix-patches via
2022-07-23 12:46 ` [bug#56717] [PATCH 1/2] gnu: Add python-i3ipc Hilton Chain via Guix-patches via
2022-07-23 12:48 ` [bug#56717] [PATCH 2/2] gnu: Add i3-autotiling Hilton Chain via Guix-patches via
2022-07-23 12:56 ` ( via Guix-patches via
2022-07-23 12:46 ` [bug#56717] [PATCH v4 1/2] gnu: Add python-i3ipc Hilton Chain via Guix-patches via
2022-07-23 12:48 ` [bug#56717] [PATCH v4 2/2] gnu: Add i3-autotiling Hilton Chain via Guix-patches via
2022-07-23 10:48 ` [bug#56717] [PATCH v2 1/2] gnu: Add python-i3ipc ( via Guix-patches via
2022-08-06 21:14 ` bug#56717: [PATCH 0/2] gnu: Add python-i3ipc and python-autotiling Ludovic Courtès
2022-08-06 21:14 ` [bug#56717] " ( via Guix-patches via
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=CLMWR6CZTJC4.3BY34EAKG35QU@guix-aspire \
--to=guix-patches@gnu.org \
--cc=56717@debbugs.gnu.org \
--cc=hako@ultrarare.space \
--cc=paren@disroot.org \
/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.