Le Wed, Jun 03, 2026 at 07:28:40PM +0200, Volker Schlecht a écrit : > Hi, > > picking up the thread started by Robert Lillack, here is the diff I have been > testing and which so far works fine here.
now that i've built-tested it: - 0.20 needs an update-plist, otherwise it lacks a bunch of headers required to build sway 1.12 (from the diff in another thread) - it updates 0.19 from .2 to .3, that's minor but still needs a bit of testing - as yaydn said it lacks wlroots/Makefile with the SUBDIRs so that ports are properly linked to the build > +++ 0.19/pkg/PLIST 3 Jun 2026 17:21:39 -0000 > @@ -0,0 +1,134 @@ > +@option no-default-conflict > +@option is-branch > +@conflict wlroots->=0.19,<0.20 > +@conflict wlroots->=0.19v0,<0.20v0 > +@pkgpath wayland/wlroots this @pkgpath makes sense to update wayland/wlroots to wayland/wlroots/0.19, just drop the first @conflict line from both PLISTs, i think we only need the @conflict to match the "other" PKGSPEC. but having the same @pkgpath wayland/wlroots in 0.20/pkg/PLIST doesnt make sense imo, you don't want to migrate wayland/wlroots to wayland/wlroots/0.20 (since there's already a @pkgpath wayland/wlroots in 0.19/pkg/PLIST) - and 0.20 will get installed as a dependency of a consumer anyway. with that said i've been able to build cage 0.3, labwc 0.20 & sway 1.12 against wlroots 0.20 - no runtime testing yet though. i think now is a good time in the release cycle to move ahead with this..
