From: Efraim Flashner <efraim@flashner.co.il>
To: Herman Rimm <herman@rimm.ee>
Cc: 75283@debbugs.gnu.org
Subject: [bug#75283] [PATCH rust-team] gnu: rust-xremap: Use output for each feature.
Date: Sun, 5 Jan 2025 10:56:46 +0200 [thread overview]
Message-ID: <Z3pJTnEc7Yg0544c@3900XT> (raw)
In-Reply-To: <940b18daf5a018d28047b31ff0585893530e5c2a.1735823152.git.herman@rimm.ee>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Do we actually need a separate output/package for each desktop type? Or
can we just add in all the features and provide just one package for all
of them?
I compared the outputs of xremap-wlroots and xremap-gnome and the shell
completions are the same between them.
On Thu, Jan 02, 2025 at 02:06:09PM +0100, Herman Rimm wrote:
> * gnu/packages/rust-apps.scm (output-features): Add procedure.
> (rust-xremap)[outputs]: Add.
> [arguments]: Remove features, add modules and output-features phases.
> (xremap-gnome, xremap-kde, xremap-wlroots, xremap-hyprland, xremap-sway,
> xremap-x11): Deprecate.
>
> Change-Id: I9cf6a27f908a0fa42e89daba12fba3615d05ad4e
> ---
> gnu/packages/rust-apps.scm | 79 +++++++++++++++++++++-----------------
> 1 file changed, 44 insertions(+), 35 deletions(-)
>
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-05 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 13:06 [bug#75283] [PATCH rust-team] gnu: rust-xremap: Use output for each feature Herman Rimm via Guix-patches via
2025-01-05 8:56 ` Efraim Flashner [this message]
2025-01-06 19:42 ` Herman Rimm 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
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=Z3pJTnEc7Yg0544c@3900XT \
--to=efraim@flashner.co.il \
--cc=75283@debbugs.gnu.org \
--cc=herman@rimm.ee \
/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).