On Mon, Jul 14, 2025 at 11:36 AM Colin Watson <cjwat...@debian.org> wrote: > No, only if the original wlroots and reshade projects were ones that > were intended to be used via vendoring/embedding.
For wlroots gamescope fork just adds performance optimization which has been landed in wlroots 0.19 (contributed by gamescope maintainers). I can't say how much this optimization is needed, I guess we will have to just wait when gamescope updates to wlroots 0.19. But for reshade it's just a static fork and I don't see any intention of updating it in the future from gamescope. So I guess I should go with the route Simon took from the neighboring thread. On Mon, Jul 14, 2025 at 10:00 AM Simon Richter <s...@debian.org> wrote: > Right now I have the package split so the various dependencies come as > separate source packages, and the various libraries unified. The plan > would be to rename all the source packages and add an "ngscopeclient" > suffix to show that these are meant mostly as build dependencies and > should not be used for anything else And package reshade-gamescope. > >vkroots - because the creator of a project intends it to be used via > >embedding (but it's already packaged with specific commit needed by > >gamescope, so it's fine for now) > > I'm not quite sure from looking at https://github.com/misyltoad/vkroots, > but that may be OK. If it's easy to use the packaged version, that's > better. You can see they intention here https://github.com/misyltoad/vkroots/issues/4#issuecomment-1453619518 https://github.com/misyltoad/vkroots/issues/4#issuecomment-1453841820 Cheers Ilya
