Re: weston-info as a standalone utility
Hi all, On Mon, 20 Jul 2020 at 13:50, Olivier Fourdan wrote: > Cool! Done, here: > https://gitlab.freedesktop.org/ofourdan/wayland-utils Is there anything more to do before we can get that moved under the wayland domain? Cheers Olivier ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
Hi Pekka, On Mon, 20 Jul 2020 at 13:34, Pekka Paalanen wrote: > > On Mon, 20 Jul 2020 10:13:19 +0200 > Olivier Fourdan wrote: > > > Hi all, > > > > On Tue, 14 Jul 2020 at 10:39, Michel Dänzer wrote: > > > > > > And from the corresponding glxinfo / vulkaninfo & friends, which don't > > > have their own repositories either. The only exception that comes to > > > mind offhand is xdpyinfo, but that's just because every single app got > > > its own repository when the monolithic X tree was split up, which > > > these days seems to be generally considered as having gone overboard. > > > > Right, so, to move forward with this, I shall: > > > > - Rename the repository to “wayland-utils” > > - Move the source into its own subdirectory (so we can have more later) > > > > Sounds good. Cool! Done, here: https://gitlab.freedesktop.org/ofourdan/wayland-utils If that works for everyone, I'll remove the old “wayland-info” repo. > > Regarding weston-info, shouldn't we add a deprecation warning before > > actually removing it? Or maybe add a symlink weston-info→wayland-info > > ? > > Personally I'd be fine leaving that with distribution packagers. > That way we upstream don't have to deal with weston<->wayland-utils > conflicts or dependencies. As there is no conflict to begin > with, we're not in a hurry to remove weston-info. We can do that in > the next Weston release after the first wayland-utils release. That's certainly fine by me. :) Cheers Olivier ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
On Mon, 20 Jul 2020 10:13:19 +0200 Olivier Fourdan wrote: > Hi all, > > On Tue, 14 Jul 2020 at 10:39, Michel Dänzer wrote: > > > > And from the corresponding glxinfo / vulkaninfo & friends, which don't > > have their own repositories either. The only exception that comes to > > mind offhand is xdpyinfo, but that's just because every single app got > > its own repository when the monolithic X tree was split up, which > > these days seems to be generally considered as having gone overboard. > > Right, so, to move forward with this, I shall: > > - Rename the repository to “wayland-utils” > - Move the source into its own subdirectory (so we can have more later) > Sounds good. > Regarding weston-info, shouldn't we add a deprecation warning before > actually removing it? Or maybe add a symlink weston-info→wayland-info > ? Personally I'd be fine leaving that with distribution packagers. That way we upstream don't have to deal with weston<->wayland-utils conflicts or dependencies. As there is no conflict to begin with, we're not in a hurry to remove weston-info. We can do that in the next Weston release after the first wayland-utils release. Thanks, pq pgp1EpideyYM7.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
Hi all, On Tue, 14 Jul 2020 at 10:39, Michel Dänzer wrote: > > And from the corresponding glxinfo / vulkaninfo & friends, which don't > have their own repositories either. The only exception that comes to > mind offhand is xdpyinfo, but that's just because every single app got > its own repository when the monolithic X tree was split up, which > these days seems to be generally considered as having gone overboard. Right, so, to move forward with this, I shall: - Rename the repository to “wayland-utils” - Move the source into its own subdirectory (so we can have more later) Regarding weston-info, shouldn't we add a deprecation warning before actually removing it? Or maybe add a symlink weston-info→wayland-info ? Cheers Olivier ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
Hi Pekka On Mon, 13 Jul 2020 at 08:53, Pekka Paalanen wrote: > > could you explain a bit more about how weston-info is so different > from the other simple demos? Precisely, it is not a demo, nor a test, it's a useful tool for regular users and developers. > I'll throw in an extra idea: Weston should be good for testing > other projects in CI, as a headless display server to run your > project to be tested against. We haven't done it upstream, so I'm > not sure it's as easy as it should be. The repository hosting > wayland-info would be perfect for this: have the CI run > wayland-info against a version-locked Weston release and verify > the output is as expected. Wayland-info gets CI to begin with, and > we see how Weston bends to the task. You can also add other Wayland > compositors to CI to test wayland-info against. Sure, I mean, I am not very familiar with the CI and its implications, but why not :) Cheers Olivier ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2020-07-13 8:53 a.m., Pekka Paalanen wrote: > On Mon, 13 Jul 2020 16:03:40 +1000 Peter Hutterer > wrote: > >> On Thu, Jul 09, 2020 at 05:14:32PM +0200, Olivier Fourdan wrote: >>> Hey, >>> >>> On Thu, 9 Jul 2020 at 16:41, Daniel Stone >>> wrote: On Thu, 9 Jul 2020 at 15:38, Pekka Paalanen wrote: > +1 for having this under the wayland organization in > Gitlab. +1 for deleting weston-info from Weston > repository. > > Shall we keep the new repository only for "info" tools, or > should it contain more, like Weston's simple-shm, > simple-egl, and a rewrite of weston-eventdemo that doesn't > use toytoolkit? > > I would be fine with moving all "simple" clients from > Weston repository to there if that's appropriate. +1 to all of the above. I'd be happy to see it in a utils and examples repo, with at least the ones you mentioned here. I don't think toytoolkit should ever be pushed in there, because then we run the danger of people thinking it might be a good idea. >>> >>> Thanks for your support! >>> >>> Having another "utils and example" repo is a good idea, but I >>> think weston-info stands apart from the other programs you >>> mentioned, simple-shm, simple-egl or eventdemo are more testing >>> or debugging tools, I reckon. >>> >>> I mean weston-info is simple and generic enough that it >>> deserves a repo of its own. Besides, having it in its own repo >>> would allow for new releases whenever we see fit, i.e. when we >>> want to add more information for new protocols, without having >>> to deal with other unrelated tools. >> >> I agree with olivier here, wayland-info should always work, >> against any compositor and just list the basic information about >> the protocols - and all of them, ideally. No interactivity, no >> toolkits, no debugging beyond the most basic grep. >> >> Any other tools can well go into a wayland-utils repo but they're >> different to wayland-info. > > Hi Olivier, > > could you explain a bit more about how weston-info is so different > from the other simple demos? And from the corresponding glxinfo / vulkaninfo & friends, which don't have their own repositories either. The only exception that comes to mind offhand is xdpyinfo, but that's just because every single app got its own repository when the monolithic X tree was split up, which these days seems to be generally considered as having gone overboard. > I'll throw in an extra idea: Weston should be good for testing > other projects in CI, as a headless display server to run your > project to be tested against. We haven't done it upstream, so I'm > not sure it's as easy as it should be. FWIW, I'm currently working on using weston like this for Xwayland testing in xserver, seems to work fine so far. - -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer -BEGIN PGP SIGNATURE- iF0EARECAB0WIQSwn681vpFFIZgJURRaga+OatuyAAUCXw1vQQAKCRBaga+Oatuy AH5bAJ9To1/E41U771/JMJGh5UArfcsqfACfXyjlmrQuHM7myksK+cxefOFyFzI= =Gb3A -END PGP SIGNATURE- ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
On Mon, 13 Jul 2020 16:03:40 +1000 Peter Hutterer wrote: > On Thu, Jul 09, 2020 at 05:14:32PM +0200, Olivier Fourdan wrote: > > Hey, > > > > On Thu, 9 Jul 2020 at 16:41, Daniel Stone wrote: > > > > > > On Thu, 9 Jul 2020 at 15:38, Pekka Paalanen wrote: > > > > +1 for having this under the wayland organization in Gitlab. > > > > +1 for deleting weston-info from Weston repository. > > > > > > > > Shall we keep the new repository only for "info" tools, or should > > > > it contain more, like Weston's simple-shm, simple-egl, and a > > > > rewrite of weston-eventdemo that doesn't use toytoolkit? > > > > > > > > I would be fine with moving all "simple" clients from Weston > > > > repository to there if that's appropriate. > > > > > > +1 to all of the above. I'd be happy to see it in a utils and examples > > > repo, with at least the ones you mentioned here. I don't think > > > toytoolkit should ever be pushed in there, because then we run the > > > danger of people thinking it might be a good idea. > > > > Thanks for your support! > > > > Having another "utils and example" repo is a good idea, but I think > > weston-info stands apart from the other programs you mentioned, > > simple-shm, simple-egl or eventdemo are more testing or debugging > > tools, I reckon. > > > > I mean weston-info is simple and generic enough that it deserves a > > repo of its own. Besides, having it in its own repo would allow for > > new releases whenever we see fit, i.e. when we want to add more > > information for new protocols, without having to deal with other > > unrelated tools. > > I agree with olivier here, wayland-info should always work, against any > compositor and just list the basic information about the protocols - and all > of them, ideally. No interactivity, no toolkits, no debugging beyond the > most basic grep. > > Any other tools can well go into a wayland-utils repo but they're different > to wayland-info. Hi Olivier, could you explain a bit more about how weston-info is so different from the other simple demos? I'll throw in an extra idea: Weston should be good for testing other projects in CI, as a headless display server to run your project to be tested against. We haven't done it upstream, so I'm not sure it's as easy as it should be. The repository hosting wayland-info would be perfect for this: have the CI run wayland-info against a version-locked Weston release and verify the output is as expected. Wayland-info gets CI to begin with, and we see how Weston bends to the task. You can also add other Wayland compositors to CI to test wayland-info against. Thanks, pq pgpLk68DrjcwT.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
On Thu, Jul 09, 2020 at 05:14:32PM +0200, Olivier Fourdan wrote: > Hey, > > On Thu, 9 Jul 2020 at 16:41, Daniel Stone wrote: > > > > On Thu, 9 Jul 2020 at 15:38, Pekka Paalanen wrote: > > > +1 for having this under the wayland organization in Gitlab. > > > +1 for deleting weston-info from Weston repository. > > > > > > Shall we keep the new repository only for "info" tools, or should > > > it contain more, like Weston's simple-shm, simple-egl, and a > > > rewrite of weston-eventdemo that doesn't use toytoolkit? > > > > > > I would be fine with moving all "simple" clients from Weston > > > repository to there if that's appropriate. > > > > +1 to all of the above. I'd be happy to see it in a utils and examples > > repo, with at least the ones you mentioned here. I don't think > > toytoolkit should ever be pushed in there, because then we run the > > danger of people thinking it might be a good idea. > > Thanks for your support! > > Having another "utils and example" repo is a good idea, but I think > weston-info stands apart from the other programs you mentioned, > simple-shm, simple-egl or eventdemo are more testing or debugging > tools, I reckon. > > I mean weston-info is simple and generic enough that it deserves a > repo of its own. Besides, having it in its own repo would allow for > new releases whenever we see fit, i.e. when we want to add more > information for new protocols, without having to deal with other > unrelated tools. I agree with olivier here, wayland-info should always work, against any compositor and just list the basic information about the protocols - and all of them, ideally. No interactivity, no toolkits, no debugging beyond the most basic grep. Any other tools can well go into a wayland-utils repo but they're different to wayland-info. Cheers, Peter ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
Hey, On Thu, 9 Jul 2020 at 16:41, Daniel Stone wrote: > > On Thu, 9 Jul 2020 at 15:38, Pekka Paalanen wrote: > > +1 for having this under the wayland organization in Gitlab. > > +1 for deleting weston-info from Weston repository. > > > > Shall we keep the new repository only for "info" tools, or should > > it contain more, like Weston's simple-shm, simple-egl, and a > > rewrite of weston-eventdemo that doesn't use toytoolkit? > > > > I would be fine with moving all "simple" clients from Weston > > repository to there if that's appropriate. > > +1 to all of the above. I'd be happy to see it in a utils and examples > repo, with at least the ones you mentioned here. I don't think > toytoolkit should ever be pushed in there, because then we run the > danger of people thinking it might be a good idea. Thanks for your support! Having another "utils and example" repo is a good idea, but I think weston-info stands apart from the other programs you mentioned, simple-shm, simple-egl or eventdemo are more testing or debugging tools, I reckon. I mean weston-info is simple and generic enough that it deserves a repo of its own. Besides, having it in its own repo would allow for new releases whenever we see fit, i.e. when we want to add more information for new protocols, without having to deal with other unrelated tools. Cheers Oliveir ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
Hi, On Thu, 9 Jul 2020 at 15:38, Pekka Paalanen wrote: > On Thu, 9 Jul 2020 10:32:56 +0200 > Olivier Fourdan wrote: > > In the meantime, Peter has already submitted patches to wayland-info > > (thanks Peter!) so the tip of wayland-info is different from > > weston-info (basically, we have diverged already). > > > > Eventually, if nobody has objections, we could move that repo to the > > wayland domain… > > thanks for doing this, looks good! > > +1 for having this under the wayland organization in Gitlab. > +1 for deleting weston-info from Weston repository. > > Shall we keep the new repository only for "info" tools, or should > it contain more, like Weston's simple-shm, simple-egl, and a > rewrite of weston-eventdemo that doesn't use toytoolkit? > > I would be fine with moving all "simple" clients from Weston > repository to there if that's appropriate. +1 to all of the above. I'd be happy to see it in a utils and examples repo, with at least the ones you mentioned here. I don't think toytoolkit should ever be pushed in there, because then we run the danger of people thinking it might be a good idea. Cheers, Daniel ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Re: weston-info as a standalone utility
On Thu, 9 Jul 2020 10:32:56 +0200 Olivier Fourdan wrote: > Hi all, > > A long time ago [1], I suggested that we move weston-info out of the > Weston source tree because this is a very useful tool which gives > important information about any Wayland compositor, not just Weston. > > The general consensus was it was a good idea, unfortunately other more > important things happened, people (including me) eventually forgot > about that and it never actually came to fruition… > > But the need remains, I think we should have a compositor agnostic > tool that gives the general information about the running compositor. > And we should not need to install Weston for that alone. > > So I took the liberty to uproot weston-info, rename it as wayland-info > and put it on its own repo: > > https://gitlab.freedesktop.org/ofourdan/wayland-info > > As you can see, I took great care to preserve the git history of > weston-info in the process. > > In the meantime, Peter has already submitted patches to wayland-info > (thanks Peter!) so the tip of wayland-info is different from > weston-info (basically, we have diverged already). > > Eventually, if nobody has objections, we could move that repo to the > wayland domain… Hi Olivier, thanks for doing this, looks good! +1 for having this under the wayland organization in Gitlab. +1 for deleting weston-info from Weston repository. Shall we keep the new repository only for "info" tools, or should it contain more, like Weston's simple-shm, simple-egl, and a rewrite of weston-eventdemo that doesn't use toytoolkit? I would be fine with moving all "simple" clients from Weston repository to there if that's appropriate. Thanks, pq pgpDhWcXzA46S.pgp Description: OpenPGP digital signature ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
