From: Barbaross93 <Barbaross93@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: keyd-2.4.0
Date: Wed, 15 Jun 2022 01:25:20 +0200 [thread overview]
Message-ID: <20220614232520.0_aPAQwnLspzN4B3-vhvrnTbjMQyTrzKJa1hpZpD15w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37195@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
There is an updated pull request by Barbaross93 against master on the void-packages repository
https://github.com/Barbaross93/void-packages keyd
https://github.com/void-linux/void-packages/pull/37195
New package: keyd-2.4.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86-64)
A patch file from https://github.com/void-linux/void-packages/pull/37195.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-keyd-37195.patch --]
[-- Type: text/x-diff, Size: 1432 bytes --]
From b9e237d2769f99ffed7cc4e785bc34741a7f7371 Mon Sep 17 00:00:00 2001
From: Barbaross <cullenrss@gmail.com>
Date: Thu, 19 May 2022 01:52:28 -0400
Subject: [PATCH] New package: keyd-2.4.0
---
srcpkgs/keyd/files/keyd/run | 2 ++
srcpkgs/keyd/template | 20 ++++++++++++++++++++
2 files changed, 22 insertions(+)
create mode 100644 srcpkgs/keyd/files/keyd/run
create mode 100644 srcpkgs/keyd/template
diff --git a/srcpkgs/keyd/files/keyd/run b/srcpkgs/keyd/files/keyd/run
new file mode 100644
index 000000000000..868cb747ab6c
--- /dev/null
+++ b/srcpkgs/keyd/files/keyd/run
@@ -0,0 +1,2 @@
+#!/bin/sh
+exec keyd
diff --git a/srcpkgs/keyd/template b/srcpkgs/keyd/template
new file mode 100644
index 000000000000..e8c4a1c45a39
--- /dev/null
+++ b/srcpkgs/keyd/template
@@ -0,0 +1,20 @@
+# Template file for 'keyd'
+pkgname=keyd
+version=2.4.0
+revision=1
+build_style=gnu-makefile
+make_use_env=yes
+short_desc="Key remapping daemon for linux"
+maintainer="Barbaross <cullenrss@gmail.com>"
+license="MIT"
+homepage="https://github.com/rvaiya/keyd"
+changelog="https://raw.githubusercontent.com/rvaiya/keyd/master/docs/CHANGELOG.md"
+distfiles="https://github.com/rvaiya/keyd/archive/refs/tags/v${version}.tar.gz"
+checksum=100007894ac4fa6e95f5de5c2fe992c8b00e68d9df76c4bcdd8402a29d7b4058
+system_groups="keyd"
+
+post_install() {
+ vsv keyd
+ vlicense LICENSE
+ vinstall keyd.quirks 644 usr/share/libinput 30-keyd.quirks
+}
next prev parent reply other threads:[~2022-06-14 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 6:00 [PR PATCH] " Barbaross93
2022-05-19 6:05 ` Barbaross93
2022-06-14 18:14 ` [PR REVIEW] " classabbyamp
2022-06-14 18:21 ` classabbyamp
2022-06-14 23:14 ` [PR PATCH] [Updated] " Barbaross93
2022-06-14 23:15 ` Barbaross93
2022-06-14 23:18 ` [PR PATCH] [Updated] " Barbaross93
2022-06-14 23:25 ` Barbaross93 [this message]
2022-06-15 0:25 ` Barbaross93
2022-06-15 0:37 ` classabbyamp
2022-06-15 1:56 ` [PR PATCH] [Merged]: " 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=20220614232520.0_aPAQwnLspzN4B3-vhvrnTbjMQyTrzKJa1hpZpD15w@z \
--to=barbaross93@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).