From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wally-cli: don't vendor udev rules
Date: Sat, 15 May 2021 12:27:22 +0200 [thread overview]
Message-ID: <20210515102722.22qr4eyLCuA_v26FT0lYfmj3M7c1zP7-SpNnIKk3pNo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30879@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/30879#issuecomment-841636293
Comment:
Ah, yeah: The udev rules for these keyboards are not only required for the wally-cli tool, but also for the graphical wally tool, as well as their web-based trainer and their web-based keyboard configurator (another flashing tool). The udev rules are only included in the repo of the graphical wally tool, so ideally there'd be 3 packages, wally, wally-cli and wally-udev, with the former two depending on the latter. This way people can install precisely what they need, and don't need to install stuff they don't need. I use the web based configurator and trainer, so all I need is the udev rules.
next prev parent reply other threads:[~2021-05-15 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 20:51 [PR PATCH] Wally cli 2.0.0 2 jcgruenhage
2021-05-14 21:07 ` [PR PATCH] [Updated] wally-cli: don't vendor udev rules jcgruenhage
2021-05-14 23:55 ` jcgruenhage
2021-05-15 1:55 ` jcgruenhage
2021-05-15 7:29 ` Gottox
2021-05-15 9:31 ` jcgruenhage
2021-05-15 9:37 ` Gottox
2021-05-15 9:40 ` Gottox
2021-05-15 10:27 ` jcgruenhage [this message]
2021-05-16 7:54 ` Gottox
2021-05-17 9:34 ` jcgruenhage
2021-05-27 10:56 ` Gottox
2021-05-27 10:57 ` Gottox
2021-10-14 22:19 ` [PR PATCH] [Closed]: " Piraty
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=20210515102722.22qr4eyLCuA_v26FT0lYfmj3M7c1zP7-SpNnIKk3pNo@z \
--to=jcgruenhage@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).