From: Jipok <Jipok@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: Niri
Date: Wed, 31 Jan 2024 17:31:42 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48456@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]
New issue by Jipok on void-packages repository
https://github.com/void-linux/void-packages/issues/48456
Description:
### Package name
niri
### Package homepage
https://github.com/YaLTeR/niri
### Description
Very cool window manager concept. If you add such binds:
```
Mod+A { focus-column-left; }
Mod+S { focus-window-or-workspace-down; }
Mod+W { focus-window-or-workspace-up; }
Mod+D { focus-column-right; }
```
then moving through windows and workspaces can be represented as moving along a grid using WASD (as in games). Which is very convenient and the animation makes everything amazing.
However, the authors' attitude towards X11(`X11 is very cursed`) and the lack of [Xwayland](https://github.com/YaLTeR/niri/wiki/Xwayland) support makes it unsuitable for my use.
Despite the fact that the readme clearly mentions a systemd dependency, I was able to build and run it under void without any problems. For those interested, I will leave my template here:
```
# Template file for 'niri'
pkgname=niri
version=0.1.0
revision=1
#archs="i686 x86_64"
build_style=cargo
hostmakedepends="pkg-config"
makedepends="eudev-libudev-devel libxkbcommon-devel libinput-devel pipewire-devel pango-devel libseat-devel clang libgbm-devel"
depends="eudev-libudev libxkbcommon libinput libpipewire pango libseat libgbm"
short_desc="scrollable-tiling Wayland compositor"
maintainer="Jipok <void@jipok.ru>"
license="GPL-3.0-or-later"
homepage="https://github.com/YaLTeR/niri"
changelog="https://github.com/YaLTeR/niri/releases"
distfiles="https://github.com/YaLTeR/niri/archive/refs/tags/v${version}.tar.gz"
checksum=b26d39e6855de6de581b253d06cbaa375709b00a276626326b745e0d10b0ac70
post_install() {
vmkdir etc/niri
vcopy resources/default-config.kdl etc/niri/config.kdl
}
```
### Does the requested package meet the package requirements?
Compiled
### Is the requested package released?
Yes
next reply other threads:[~2024-01-31 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 16:31 Jipok [this message]
2024-02-03 13:15 ` Eloitor
2024-02-03 13:16 ` Eloitor
2024-02-04 16:04 ` Eloitor
2024-02-11 1:29 ` lidgnulinux
2024-02-11 11:47 ` Jipok
2024-02-20 12:33 ` YaLTeR
2024-02-20 13:33 ` Eloitor
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-48456@inbox.vuxu.org \
--to=jipok@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).