Arch Linux User Repository

Hmm... great. Website overhaul which restructures the website organisation. Projects aren't subdomains anymore. But raichoos projects weren't moved. And the new certificate doesn't cover the old domains anymore...
Well... http download it will be

Download fails with:

curl: (60) SSL: no alternative certificate subject name matches target hostname 'hikari.acmelabs.space'

Thanks for the hint micwoj92.
I uploaded the latest official PKGBUILD.
Although it is possible that this dep may change, as there are initial patches floating around for hikari that update the wlroots-version to 0.16

Missing dependency wlroots0.15

Building this package fails if you have MAKEFLAGS="-l10" (load limit instead of job limit) set in makepkg.conf because bmake is not GNU make and doesn't understand this option, so it exits with error code 2 and message "usage: bmake [-BeikNnqrSstWwX]". I would appreciate if you could update this PKGBUILD to strip options bmake doesn't understand from MAKEFLAGS.

Yeah, it is currently not easy with the various compositors (looking at you wayfire and your restrictions). Or mostly because of the backward incompatible changes of wlroots.
Good that you still could somehow sort it out. (And I don't mention that there was a third option... The wlroots-git PKGBUILD could have been pinned to a specific tag (v0.14.1 for example). Kinda forgot about this possibility >.>)
As a sidenote: If there are patches (or rather fixes) for labwc which are worth picking up, you can always leave a comment for that package. And if I can rather easily backport those, they may be added :D

Okay, updating wlroots-git was a washout. But after a few hours sleep, I took half an hour or so to rebuild everything to use the stable wlroots version. I was then able to install hikari without problems.

While I have successfully booted into the environment, I haven;t had a chance to check out the configuration, and, more importantly, whether the layer-shell protocol works with my panel and task-bar, but, touch wood, things are looking good.

Thanks for your prompt attention Irvine

Okay, I to need sleep on this for a couple of hours first:

Updating wlroots-git is not a problem, and I will do so as soon as I can.

With regard to switching to the stable wlroots, I would love to. The problem is that the current stable labwc is not properly implementing the layer-shell protocol. In the git-version, the bug was fixed a week or so ago.

My other wlroots compositors are wayfire and sway. So, mainly because of the wayfire dependency chain, but also the various peripherals needed for a working environment, switching between wlroots versions is non-trivial

Anyway, I hope you can see why I really need to sleep on switching to the stable wlrootsfor a bit first.

Irvine

Not that surprising, that it even happens with the VCS package. Development seems to have slowed down.
But looking at the version of your wlroots-git package, could you please update it? Upstream introduces rather often breaking changes and the compositors don't add support for older wlroots packages.
Which can also mean, that current wlroots-git also has breaking changes again. So better would be, if possible, you switched to the stable wlroots package.

wlroots-git 0.14.0.r303.gf7ea33da-1

It may be worth noting that I get the exact same error with * hikari-darcs*

Irvine