Hi Guido, On Friday, 15 December 2023 17:30:08 CET Guido Günther wrote: > On Fri, Dec 15, 2023 at 04:59:40PM +0100, Diederik de Haas wrote: > > On dinsdag 12 december 2023 18:44:25 CET you wrote: > > > Please update sway to work with wlroots 0.17. 0.17.0 is currently in > > > experimental an will be uploaded to unstable by the end of December > > > 2023. > > > > FYI: I looked a bit into this issue ... > > > > After backporting the second I got a bad _feeling_ that this strategy may > > be used to get it to compile, but would that still make it run > > (properly)? > > > > While researching this I also noticed several commits titled > > "chase wlroots ..." like commit 6f6b82793d95e3c10d54bcf21ca3f0c76c44b882 > > referencing an upstream wlroots MR with the 'breaking' label attached > > There's a larger amount of API changes that are needed for the 0.16 -> > 0.17 switch, see > https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3527#breaking-chang > es-for-compositors
That's way more then my limited research revealed :-O > so I agree: trying to backport that is a considerable amount > f work. I'd either look at packaging a 1.9 git snapshot and maybe check > with upstream if they intend to release a 0.17 based version. > > AFAIK sway's development branch tracks the current (in development) > 0.18.x already (which will be another soname bump). I initially grabbed the mason.build commit from master when I realized that was too far ahead and then found (and grabbed) the one from the v1.9 branch. Given that there have been 0 commits to the v1.8 branch since the 1.8.1 release, it looks very unlikely that that'll be updated for wlroots 0.17. And it looks like v1.9 is (and will be) targetting wlroots 0.17 and indeed master went ahead towards 0.18. Cheers, Diederik
signature.asc
Description: This is a digitally signed message part.
