Re: xserver: do we still need Fopen() ?

2024-02-05 Thread Enrico Weigelt, metux IT consult
On 02.02.24 21:05, Alan Coopersmith wrote: Hi, I suspect for the OS'es that the xserver code builds on today, that could be replaced by #ifndef WIN32, which would then allow the first half of that #ifdef in Fopen to be deleted, leaving just the simpler case, since Fopen is already not built for

RFC: xserver release planning

2024-02-05 Thread Enrico Weigelt, metux IT consult
Hello folks, since Xorg server didn't have a (major) release for quite some time, I'd like to discuss how to proceed here. The major problems I'm seeing right now: #1 lots of open issues and PRs, but no release planning #2 a bunch of fixes (mostly bsd) in master, which look like they could

Meson vs. automake/autoconf

2024-02-05 Thread tlaronde
I'm continuing my review and I'm now looking at libxcb and xcbproto. Is there a goal set to switch from auto* tools to meson/ninja for the maximum of projects? Since I have to untangle things for my own built framework, I may as well provide meson files (that are undoubtely more readable than the

issues and merge requests

2024-02-05 Thread tlaronde
Alan Coopersmith has applied the merge request for libXau---thanks! I had written 2 issues, related, against libXau, that the patches address, so I have closed the issues after the merge. It seems to me that writing issues against a module; providing patches via a merge request; then closing the

Re: Meson vs. automake/autoconf

2024-02-05 Thread Alan Coopersmith
On 2/5/24 12:45, tlaro...@kergis.com wrote: I'm continuing my review and I'm now looking at libxcb and xcbproto. Is there a goal set to switch from auto* tools to meson/ninja for the maximum of projects? Yes - that's our overall direction, but progress is going slowly. There is some though -

Re: issues and merge requests

2024-02-05 Thread Peter Hutterer
On Mon, Feb 05, 2024 at 09:52:50PM +0100, tlaro...@kergis.com wrote: > Alan Coopersmith has applied the merge request for libXau---thanks! > > I had written 2 issues, related, against libXau, that the patches > address, so I have closed the issues after the merge. > > It seems to me that writing

Re: xserver extensions/hooks: freeing client resources

2024-02-05 Thread Aaron Plattner
On 2/1/24 7:03 AM, Enrico Weigelt, metux IT consult wrote: Hello folks, I'm currently writing an extension that's storing per-client data. Where's is the right place to free up all resources ? I guess the client state xace hook - but what's the difference between retained and gone ? I don't