Closed tumashu closed 1 year ago
Hi tumashu
Thank you for your report.
It seems that you are using an older version (1.8.0) of cagebreak, does this issue affect the newest version (2.0.1 currently) too?
cheers project-repo
does this issue affect the newest version (2.0.1 currently) too?
yes
Hi tumashu
We just pushed some code to the development branch which cleans up the logic behind the loading of the default configuration file. Could you check if this resolves the problem?
Cheers project-repo
PS: If you want, you can use this PKGBUILD to build the development branch:
# Maintainer: project-repo <archlinux-aur@project-repo.co>
pkgname=cagebreak
pkgver=2.0.1
pkgrel=1
pkgdesc='Tiling wayland compositor based on cage inspired by ratpoison'
arch=('x86_64')
url='https://github.com/project-repo/cagebreak'
license=('MIT')
depends=('wayland' 'libxkbcommon' 'wlroots<0.17.0' 'pango')
makedepends=('meson' 'ninja' 'scdoc' 'wayland-protocols')
optdepends=('wl-clipboard: clipboard support'
'xorg-xwayland: x application support')
options=('!buildflags' '!strip')
conflicts=('cagebreak-bin')
source=("cagebreak::git+https://github.com/project-repo/cagebreak")
sha512sums=('SKIP')
build() {
cd "$pkgname"
git checkout development
meson setup build -Dxwayland=true -Dman-pages=true
ninja -C build
}
package() {
cd "$pkgname"
mkdir -p "$pkgdir/usr/bin/"
cp 'build/cagebreak' "$pkgdir/usr/bin/"
}
works!
Hi tumashu,
great to hear that this is working now.
We are tying up a few loose ends and will be releasing a bugfix with Cagebreak 2.0.2 in due course.
cheers project-repo
@project-repo when release 2.0.2?
Hi, Thanks for the ping, things have been rather busy recently... Following you're question, we've been looking into getting a release out sometime in the next few days to weeks, but as of now we can't promise anything. Sorry for any inconvenience (and the long response time), project-repo
Hi tumashu
We have just released Cagebreak 2.1.0 including a fix for this issue.
Thank you for your help!
cheers project-repo
good news :-)