Hi Pekka, On Wed, 29 Nov 2023 at 15:02, Pekka Paalanen <ppaala...@gmail.com> wrote:
> On Wed, 29 Nov 2023 10:10:05 +0100 > Olivier Fourdan <four...@gmail.com> wrote: > > * xwayland-run, to spawn an X11 client within its own dedicated Xwayland > > rootful instance, > > wouldn't this one be at home in the xserver repository? > Yes, xwayland-run might be better suited in the xorg space. But the 3 utilities share the same modules in Python, so splitting them isn't convenient. > * wlheadless-run to run a Wayland client on a set of supported Wayland > > headless compositors, > > I think this would belong fine in wayland-utils except for needing > per-compositor code in it. Having tools that depend on compositor > specifics live in wayland-utils would need a consensus agreement. I > have nothing against that, but I also don't maintain wayland-utils. > The whole purpose of that is precisely to hide the differences between the compositors, so that requires per-compositor modules. Alternatively, maybe each compositor project should consider shipping a > short-cut command for a headless instance? Though that does make > xwfb-run just eat the differences instead. > > > * xwfb-run, a combination of the two other tools above to be used as a > > direct replacement for xvfb-run specifically. > > xserver repository? > Yeah, but even more than xwayland-run, wlhealess-run and xwfb-run share a lot of the same code. […] > > When I was asking to have color-and-hdr documentation repository under > any common gitlab group instead of my personal namespace, the answer > was that it should first become a true community project that won't die > as soon as I walk away from it. > > Will be interesting to see how much attention your scripts gain. > Good point indeed, I guess this can stay in my gitlab space in the meantime. And that shouldn't stop anyone downstream from packaging it. Cheers Olivier
