Hi everyone, Just a note on cairo below:
On Sun, Feb 25, 2024 at 10:39 AM, Hilton Chain wrote: > Hi everyone, > > On Sun, 25 Feb 2024 08:32:27 +0800, > Lucy Coleclough wrote: >> >>> On Sat, 24 Feb 2024 at 20:48, hutzdog <hutz...@proton.me> wrote: >>> [snip] >>> # New Patches >>> The following new patches will need to be created (I intend to submit these >>> at some point in the near future): >>> Cairo -> 1.18.0 (requires moving to Meson, I have a mostly complete set of >>> changes to make it work) > > I didn't take a closer look at cairo update, but yes, this may require some > work, at least to be able to finish its tests. > I submitted the patches as 69495: <https://issues.guix.gnu.org/69495> It works for me locally in some limited tests (e.g. icecat). Hutzdog: you mentioned getting the docs built and put in the output, but I didn't see that in your linked repo. The issue is that gtk-doc is needed which depends on cairo. I worked around the dependency cycle by hiding cairo and making a new cairo-with-documentation (the first is used for packages and hidden, the second with docs and public). Thanks to lilyp on #guix for pointing me to glib with a similar issue and workaround. But maybe I missed something if you didn't need to do this? Once cairo is approved I'll get mesa-updates building with libdrm, cairo, vulkan, and mesa updates. It would be nice to grab the libinput update so we don't have to wait for core-updates, but I didn't look if that make sense. Otherwise we could have just a libinput-next for hyprland, for instance (though I don't know where it fits in the dependency graph here). More updates soon, and thanks everyone! Cool to see about plugin systems and services, haven't looked at that yet. John
