From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package request: keyd
Date: Wed, 15 Jun 2022 03:57:09 +0200 [thread overview]
Message-ID: <20220615015709._Y_djK5xQ3_d_3LA3Alj0KztykMWmQmxR48lndMxb5k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37175@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Closed issue by Barbaross93 on void-packages repository
https://github.com/void-linux/void-packages/issues/37175
Description:
I recently stumbled upon [keyd](https://github.com/rvaiya/keyd), a sweet and simple keyboard daemon similar to kmonad. I've made a template that works, but I don't think I did things "properly", notably the usage of `make_use_env` and the manual install of the needed quirk file for libinput. If there is interest, I'll go ahead and make a PR provided I can get some feedback.
Here's the template:
```
# Template file for 'keyd'
pkgname=keyd
version=2.4.0
revision=1
build_style=gnu-makefile
make_use_env="1"
short_desc="Key remapping daemon for linux"
maintainer="Barbaross <cullenrss@gmail.com>"
license="MIT"
homepage="https://github.com/rvaiya/keyd"
distfiles="https://github.com/rvaiya/keyd/archive/refs/tags/v${version}.tar.gz"
checksum=100007894ac4fa6e95f5de5c2fe992c8b00e68d9df76c4bcdd8402a29d7b4058
post_install() {
vlicense LICENSE
vinstall ${wrksrc}/keyd.quirks 644 usr/share/libinput 30-keyd.quirks
}
```
next prev parent reply other threads:[~2022-06-15 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 1:35 [ISSUE] " Barbaross93
2022-05-18 3:03 ` classabbyamp
2022-05-18 3:04 ` classabbyamp
2022-05-18 11:52 ` Barbaross93
2022-05-18 16:48 ` classabbyamp
2022-05-19 5:48 ` Barbaross93
2022-05-19 6:17 ` classabbyamp
2022-06-15 1:57 ` classabbyamp [this message]
2022-06-15 1:57 ` classabbyamp
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=20220615015709._Y_djK5xQ3_d_3LA3Alj0KztykMWmQmxR48lndMxb5k@z \
--to=classabbyamp@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).