Re: Updating glib2 in cygwin
On 6/11/2023 1:55 PM, Jon Turney wrote: On 28/02/2022 13:29, Ken Brown wrote: The last discussion of this that I can recall started here: https://cygwin.com/pipermail/cygwin-apps/2020-May/040105.html What's needed is for someone to adopt all of the GNOME components and maintain them. As you'll see in the discussion I cited, I briefly considered updating only glib2 and a few others, but then I decided that I wasn't willing to take the responsibility of fixing/updating other components that broke as a result of this. So I pushed what I had done and left it there. It would be great if someone would step up and take over, but I'm not in a position to do that myself. Since this is possibly the most important unmaintained package (it's #1 by dependencies on this list [1]), I guess I'll adopt it. I see you got as far as 2.64.3 [2]. I'm inclined to deploy that (maybe as test) and deal with the fallout myself, while I work on bringing it completely up to date. Any issues I should be aware or, or other problems you foresee with that approach? Nothing I'm aware of. Thanks for taking this on! Ken
Re: Updating glib2 in cygwin
On 28/02/2022 13:29, Ken Brown wrote: [Redirecting to the cygwin-apps list] On 2/28/2022 3:49 AM, Marc-André Lureau wrote: Hi Ken I am a qemu developer at Red Hat. The "official" qemu Windows build uses cygwin, and the glib version there is quite old. I saw you have made some effort to update the package (https://www.cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/glib2.0.git;a=search;h=refs/heads/playground;s=Ken+Brown;st=author) What's the situation? Is there a bug tracking the issues? Hi Marc, The last discussion of this that I can recall started here: https://cygwin.com/pipermail/cygwin-apps/2020-May/040105.html What's needed is for someone to adopt all of the GNOME components and maintain them. As you'll see in the discussion I cited, I briefly considered updating only glib2 and a few others, but then I decided that I wasn't willing to take the responsibility of fixing/updating other components that broke as a result of this. So I pushed what I had done and left it there. It would be great if someone would step up and take over, but I'm not in a position to do that myself. Since this is possibly the most important unmaintained package (it's #1 by dependencies on this list [1]), I guess I'll adopt it. I see you got as far as 2.64.3 [2]. I'm inclined to deploy that (maybe as test) and deal with the fallout myself, while I work on bringing it completely up to date. Any issues I should be aware or, or other problems you foresee with that approach? [1] https://cygwin.com/packages/reports/unmaintained.html [2] https://cygwin.com/cgit/cygwin-packages/glib2.0/log/?h=playground
Re: Updating glib2 in cygwin
[Redirecting to the cygwin-apps list] On 2/28/2022 3:49 AM, Marc-André Lureau wrote: Hi Ken I am a qemu developer at Red Hat. The "official" qemu Windows build uses cygwin, and the glib version there is quite old. I saw you have made some effort to update the package (https://www.cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/glib2.0.git;a=search;h=refs/heads/playground;s=Ken+Brown;st=author) What's the situation? Is there a bug tracking the issues? Hi Marc, The last discussion of this that I can recall started here: https://cygwin.com/pipermail/cygwin-apps/2020-May/040105.html What's needed is for someone to adopt all of the GNOME components and maintain them. As you'll see in the discussion I cited, I briefly considered updating only glib2 and a few others, but then I decided that I wasn't willing to take the responsibility of fixing/updating other components that broke as a result of this. So I pushed what I had done and left it there. It would be great if someone would step up and take over, but I'm not in a position to do that myself. Ken
