Package Details: kanshi-git 1.8.0.r1.g02e8601-4

Git Clone URL: https://aur.archlinux.org/kanshi-git.git (read-only, click to copy)
Package Base: kanshi-git
Description: Dynamic output configuration for Wayland WMs
Upstream URL: https://gitlab.freedesktop.org/emersion/kanshi
Keywords: sway wayland
Licenses: MIT
Conflicts: kanshi
Provides: kanshi
Submitter: lowercase
Maintainer: vadikas
Last Packager: vadikas
Votes: 10
Popularity: 0.000005
First Submitted: 2019-03-19 14:21 (UTC)
Last Updated: 2026-01-15 19:49 (UTC)

Required by (10)

Sources (2)

Latest Comments

1 2 3 Next › Last »

yrlf commented on 2026-10-24 12:09 (UTC) (edited on 2026-10-24 12:10 (UTC) by yrlf)

@vadikas: I am of the same opinion as @fft.

The Arch Linux AUR Submission Guidelines and VCS Package Guidelines both state that the suffix -git should be used if the package does not fetch a specific release.

Your change effectively pins the package at kanshi 1.8.0 (+ one minor documentation commit) which means the package should probably be called kanshi1.8 instead of kanshi-git.

The following is my personal opinion and may sound harsh, but it is not meant as harm, rather it is meant as my personal view of how I think AUR packages should be maintained:

If you are personally unhappy with the direction kanshi development is going you are free to make your own fork and AUR package, but changing the general kanshi-git development package to no longer do what it says in the name is misleading and is doing a disservice to all users looking for such a package. If you no longer wish to maintain kanshi-git because you are only using the pinned variant personally, and are unhappy with the direction of kanshi development, perhaps it's a good time to drop maintainership instead of misleading users with unexpected changes.

Thank you.

fft commented on 2026-10-23 12:47 (UTC) (edited on 2026-10-23 12:47 (UTC) by fft)

Hello, thank you for packaging.

I think, that arch packaging guidelines assume, that newest version will be used for <app>-git packages. At least most of users will expect this.

So it's bad idea to freeze version. Propose to create 'kanshi-minimal' or 'kanshi-minimal-git' package instead and avoid using vali there (they claim, that vali is optional dependency).

vadikas commented on 2026-01-15 19:56 (UTC)

repackaged from gitlab, pinned to the last commit when it is not using vali for IPC

pychuang commented on 2025-10-15 18:16 (UTC)

Sorry for the late reply. I haven't been using this package for a long time. So I'm disowning it and let others to maintain it.

s-ol commented on 2025-07-22 08:42 (UTC) (edited on 2025-07-22 08:42 (UTC) by s-ol)

I think wlroots can be removed from makedepends, it's not mentioned anywhere in the upstream documentation and also not present in the canonical kanshi PKGBUILD. Also wlroots package versioning has changed and the way the dependency is specified here is no longer aligned with how it is used by sway for example.

pychuang commented on 2024-02-04 22:44 (UTC)

Thanks @vikbar54.9 and @yrlf. Let me know if there's any issues!

yrlf commented on 2024-02-04 21:54 (UTC) (edited on 2024-02-04 21:56 (UTC) by yrlf)

As @vikbar54.9 said, please add libscfg-git to depends.

Also, the versioning scheme in this package does not fit the Arch Linux VCS package guidelines. The version should usually contain the latest upstream version before the disambiguation tag with revision count and git hash, to be able to compare upstream versions and development versions easily.

Additionally, the provides entry can be set to also include the version.

Here is a patch that fixes all three issues in the PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 2fcd064..aee8401 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,16 +1,16 @@
 # Maintainer: Pi-Yueh Chuang <pychuang@pm.me>
 # Contributor: Ben Widawsky <ben@bwidawsk.net>
 pkgname=kanshi-git
-pkgver=r107.992c195
+pkgver=1.5.1.r6.g0602cd3
 pkgrel=1
 pkgdesc="Dynamic output configuration for Wayland WMs"
 arch=(x86_64)
 url="https://git.sr.ht/~emersion/kanshi"
 license=('MIT')
 groups=()
-depends=('wayland' 'libvarlink')
+depends=('wayland' 'libvarlink' 'libscfg-git')
 makedepends=('git' 'meson' 'ninja' 'scdoc' 'wlroots>=0.7')
-provides=("${pkgname%-git}")
+provides=("${pkgname%-git}=${pkgver%%.r*}")
 conflicts=("${pkgname%-git}")
 replaces=()
 backup=()
@@ -25,7 +25,7 @@ md5sums=('SKIP' '204747a0d0e0dd77d0e4f88f229c9c28')

 pkgver() {
     cd "$srcdir/${pkgname%-git}"
-    printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
+    git describe --long --tags --abbrev=7 | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'
 }

 build() {

vikbar54.9 commented on 2024-02-03 19:23 (UTC)

It requires libscfg now, otherwise it errors out on not finding scfg runtime dependecy.

pychuang commented on 2021-02-24 18:58 (UTC) (edited on 2021-02-24 19:00 (UTC) by pychuang)

This package comes with a systemd unit file that is not supported by the upstream. To enable the unit, run $ systemctl --user enable kanshi.service. Some notes:

  1. This unit won't automatically start unless graphical-session.target has already started. Though on many users' systems, graphical-session.target always starts under Sway, Sway actually does not activate graphical-session.target by default. The graphical-session.target may be activated silently by some other applications/units or by explicit exec command in the Sway config.
  2. Many other X11 window managers or Wayland compositors also activate graphical-session.target. This says, if you sometimes use other WM, like gnome or kde, kanshi.service will also automatically start (and then fail because kanshi is a Sway-only application).

The best practice is to create your own sway-session.target, and modify (or create your own) the kanshi.service to be wanted by sway-session.target. See the Wiki at Sway's GitHub and also ArchWiki: