Package Details: labwc-git 0.8.4.r55.gaff7cb92-2

Git Clone URL: https://aur.archlinux.org/labwc-git.git (read-only, click to copy)
Package Base: labwc-git
Description: stacking wayland compositor with look and feel from openbox (git version)
Upstream URL: https://github.com/labwc/labwc
Licenses: GPL-2.0-only
Conflicts: labwc
Provides: labwc
Submitter: TrialnError
Maintainer: TrialnError
Last Packager: TrialnError
Votes: 8
Popularity: 0.088451
First Submitted: 2020-07-23 16:04 (UTC)
Last Updated: 2025-05-31 16:59 (UTC)

Dependencies (14)

Required by (4)

Sources (1)

Latest Comments

1 2 3 Next › Last »

jjramsey commented on 2025-05-31 16:04 (UTC) (edited on 2025-05-31 19:03 (UTC) by jjramsey)

wlroots0.19 is just out of the testing repo. Yay! 😁

ETA: And labwc-git works just fine with it.

knm100 commented on 2025-05-30 02:23 (UTC) (edited on 2025-05-30 02:25 (UTC) by knm100)

warring： Library listed in 'depends' is not required by any files: liblcms2.so
So, Is the liblcms2.so necessary?

TrialnError commented on 2025-05-28 17:54 (UTC)

I had done the same locally kode54 :D And the day after was the proposal for wlroots posted. Was again some switcheroo necessary for the new name.
Great to read it is already in the respective [testing] repo. No, it cannot be expected. I suppose local modifications aren't a thing with most, considering the responses I had in other cases. I suspect this is due to aur helpers.

kode54 commented on 2025-05-28 11:46 (UTC)

Congrats, wlroots0.19 and wlroots0.18 moved from staging to extra-testing. Only a few more days until things settle.

kode54 commented on 2025-05-28 08:30 (UTC) (edited on 2025-05-28 08:31 (UTC) by kode54)

Certainly broke for me, because rather than wait, I hand packaged wlroots 0.19 and 0.18 using the current repo PKGBUILD, slightly modified. But we can't expect 99% of users to package their own software, can we?

Edit: I did this before it was even proposed to the list to drop the unversioned package in favor of releasing a wlroots0.19, so my 0.19 package was simply called wlroots.

TrialnError commented on 2025-05-26 17:51 (UTC)

You're not the first to mention that. I don't mind that happening. Intention being that I cannot forget to switch back.
It could be easily avoided. And maybe I'm doing that as it seems I'm in the minority of those who wants it to break when 0.19 is available :D

jjramsey commented on 2025-05-26 16:33 (UTC)

One catch I do see is that the header files and static library for wlroots are still installed, even though they're only needed for compilation and would potentially conflict with the wlroots0.19 package once it finally leaves the staging repo.

TrialnError commented on 2025-05-21 18:07 (UTC)

It seemed that way at first, yes. But I did miss the fact that I required additional vulkan packages whereas I thought the headers package would suffice.
I have pushed an update, which shouldn't conflict with wlroots until 0.19 hits the repos.

jjramsey commented on 2025-05-21 17:49 (UTC)

"Boils down to no stable provider of 0.19"

Yeah, I figured that would be a problem.

"it doesn't find necessary deps even if they're installed."

What do you mean by that? Does that mean that you can't get your PKGBUILD to work?

TrialnError commented on 2025-05-21 16:27 (UTC)

Thank you for the notice.
Unfortunately wlroots may stay on 0.18 for the time being until "forced" to update (in the past due to sway). And wlroots-git provides 0.20 if freshly build.
Boils down to no stable provider of 0.19. >.> Unless someone has still an older wlroots-git around. Therefore I want to temporarily switch to staticly compiled wlroots if there are no conflicts.. And guess what... it doesn't find necessary deps even if they're installed.

1 2 3 Next › Last »