Github messages for voidlinux
 help / color / mirror / Atom feed
From: noarchwastaken <noarchwastaken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [WIP] New package: ydotool-0.2.0
Date: Tue, 01 Jun 2021 05:13:44 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31237@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]

There is a new pull request by noarchwastaken against master on the void-packages repository

https://github.com/noarchwastaken/void-packages ydotool
https://github.com/void-linux/void-packages/pull/31237

[WIP] New package: ydotool-0.2.0
It seems like the package uses CPM in its CMake config for statically linking `libevdevPlus` and `libuInputPlus`, both are versioned newer than the existing ones in Void, with breaking changes. There's another dependency called `IODash` which doesn't exist in Void yet.

Is it OK to simply use CPM? Or should we update the first two and add the last one into Void, then build with those? Pinging @steinex for opinions.

We already have #25341, but it's an older version and apparently have some unfixed problems... So I wish this is a friendly takeover of that PR.

closes #31163

<!-- Mark items with [x] where applicable -->

#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/31237.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ydotool-31237.patch --]
[-- Type: text/x-diff, Size: 2187 bytes --]

From 8c9e8620b3a085af8a908c8004cc5b50bd8ea140 Mon Sep 17 00:00:00 2001
From: noarchwastaken <noarch@n0ar.ch>
Date: Mon, 31 May 2021 22:27:36 -0400
Subject: [PATCH] New package: ydotool-0.2.0

---
 srcpkgs/ydotool/files/80-uinput.rules |  3 +++
 srcpkgs/ydotool/files/ydotoold/run    |  2 ++
 srcpkgs/ydotool/template              | 31 +++++++++++++++++++++++++++
 3 files changed, 36 insertions(+)
 create mode 100644 srcpkgs/ydotool/files/80-uinput.rules
 create mode 100644 srcpkgs/ydotool/files/ydotoold/run
 create mode 100644 srcpkgs/ydotool/template

diff --git a/srcpkgs/ydotool/files/80-uinput.rules b/srcpkgs/ydotool/files/80-uinput.rules
new file mode 100644
index 000000000000..988d34547f52
--- /dev/null
+++ b/srcpkgs/ydotool/files/80-uinput.rules
@@ -0,0 +1,3 @@
+## ydotoold fix
+## https://github.com/ReimuNotMoe/ydotool/issues/25#issuecomment-535842993
+KERNEL=="uinput", GROUP="input", MODE="0660", OPTIONS+="static_node=uinput"
diff --git a/srcpkgs/ydotool/files/ydotoold/run b/srcpkgs/ydotool/files/ydotoold/run
new file mode 100644
index 000000000000..2425089b3bea
--- /dev/null
+++ b/srcpkgs/ydotool/files/ydotoold/run
@@ -0,0 +1,2 @@
+#!/bin/sh
+exec chpst -u root:input ydotoold --socket-perm 660 2>&1
diff --git a/srcpkgs/ydotool/template b/srcpkgs/ydotool/template
new file mode 100644
index 000000000000..50aa368cb35f
--- /dev/null
+++ b/srcpkgs/ydotool/template
@@ -0,0 +1,31 @@
+# Template file for 'ydotool'
+pkgname=ydotool
+version=0.2.0
+revision=1
+build_style=cmake
+hostmakedepends="git scdoc"
+short_desc="Generic command-line automation tool, works on Wayland and X11"
+maintainer="noarchwastaken <noarch@n0ar.ch>"
+license="AGPL-3.0-or-later"
+homepage="https://github.com/ReimuNotMoe/ydotool"
+distfiles="${homepage}/archive/refs/tags/v${version}.tar.gz"
+checksum=2311b003d2ff383f3348f17101f0df74f56616d530d66d0a014a52ba85a5dcf1
+
+do_install() {
+	vbin build/ydotool
+	vbin build/ydotoold
+}
+
+post_install() {
+	vsv ydotoold
+
+	vinstall ${FILESDIR}/80-uinput.rules 644 usr/lib/udev/rules.d
+
+	scdoc < manpage/ydotool.1.scd > ydotool.1
+	scdoc < manpage/ydotoold.8.scd > ydotoold.8
+
+	vman ydotool.1
+	vman ydotoold.8
+
+	vlicense LICENSE
+}

             reply	other threads:[~2021-06-01  3:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  3:13 noarchwastaken [this message]
2021-06-02  7:57 ` steinex
2021-06-02 20:45 ` noarchwastaken
2021-06-02 21:00 ` noarchwastaken
2021-06-03  9:58 ` steinex
2021-06-06 22:30 ` [PR PATCH] [Updated] " noarchwastaken
2021-06-06 22:37 ` noarchwastaken
2021-06-06 23:14 ` [PR PATCH] [Updated] " noarchwastaken
2021-06-06 23:21 ` noarchwastaken
2021-07-21  3:47 ` [PR REVIEW] " ericonr
2022-05-21  2:00 ` github-actions
2022-06-04  2:09 ` [PR PATCH] [Closed]: " github-actions

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31237@inbox.vuxu.org \
    --to=noarchwastaken@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).