Re: labwc: update to 0.6.0

[paper42 <paper42@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/40587#issuecomment-1319830389

Comment:
My proposal was to open this PR and keep adding updates to it until most of the major compositors are on 0.16 and then merge it. Last time the update took 3 months until we realized we don't want to keep waiting for every compositor to move to 0.15 and split 0.14. I would like to not wait 3 months just because some packages can not be updated this time. wayfire eventually moved to 0.15, but cage is still on 0.14. I would expect the same thing to happen here, even if just with river and because of issues on our side and not upstream's.

We unfortunately won't be able to update river because it needs zig 0.9 which needs LLVM 13 or later (we have LLVM 12) and the last version of LLVM that we would want to package doesn't build with our version of gcc. The current plan is to finish the gcc update to 12 and then package LLVM 15, then zig 0.9 and then we can update river. We are working on this, but this can take a while.

TLDR: I don't want to merge this right now, we should keep adding updates to this PR and merge it when enough compositors move.