Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] kanshi: add dependency on libvarlink to enable building kanshictl
Date: Mon, 05 Dec 2022 12:22:08 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40914@inbox.vuxu.org> (raw)

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

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

https://github.com/jcgruenhage/void-packages kanshi-1.3.0_2
https://github.com/void-linux/void-packages/pull/40914

kanshi: add dependency on libvarlink to enable building kanshictl
<!-- Uncomment relevant sections and delete options which are not applicable -->

The most recent release of kanshi added an optional kanshictl utility, which
uses varlink. If libvarlink-devel is available at build time, meson will
automatically enable that functionality and provide both the binary and the man
page for it.

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/40914.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-kanshi-1.3.0_2-40914.patch --]
[-- Type: text/x-diff, Size: 912 bytes --]

From bde6bf604223b4d7df00a5e371e3a57e6a4e9414 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Mon, 5 Dec 2022 12:18:26 +0100
Subject: [PATCH] kanshi: add dependency on libvarlink to enable building
 kanshictl

---
 srcpkgs/kanshi/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/kanshi/template b/srcpkgs/kanshi/template
index ffa57381cb0d..b3a242a9df4b 100644
--- a/srcpkgs/kanshi/template
+++ b/srcpkgs/kanshi/template
@@ -1,10 +1,10 @@
 # Template file for 'kanshi'
 pkgname=kanshi
 version=1.3.0
-revision=1
+revision=2
 build_style=meson
 hostmakedepends="pkg-config scdoc wayland-devel"
-makedepends="wayland-devel"
+makedepends="wayland-devel libvarlink-devel"
 short_desc="Output profiles automatically enabled/disabled on hotplug"
 maintainer="Stacy Harper <contact@stacyharper.net>"
 license="MIT"

             reply	other threads:[~2022-12-05 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 11:22 jcgruenhage [this message]
2022-12-05 14:54 ` [PR PATCH] [Merged]: " sgn

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-40914@inbox.vuxu.org \
    --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).