* Re: Updating glib2 in cygwin [not found] <CAMxuvawMKvGwXcv4cCpSd4pgmwuqUjvy6UeSa6viKO-OF3dp3w@mail.gmail.com> @ 2022-02-28 13:29 ` Ken Brown 2023-06-11 17:55 ` Jon Turney 0 siblings, 1 reply; 3+ messages in thread From: Ken Brown @ 2022-02-28 13:29 UTC (permalink / raw) To: Marc-André Lureau, cygwin-apps [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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Updating glib2 in cygwin 2022-02-28 13:29 ` Updating glib2 in cygwin Ken Brown @ 2023-06-11 17:55 ` Jon Turney 2023-06-11 19:27 ` Ken Brown 0 siblings, 1 reply; 3+ messages in thread From: Jon Turney @ 2023-06-11 17:55 UTC (permalink / raw) To: Ken Brown, cygwin-apps 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Updating glib2 in cygwin 2023-06-11 17:55 ` Jon Turney @ 2023-06-11 19:27 ` Ken Brown 0 siblings, 0 replies; 3+ messages in thread From: Ken Brown @ 2023-06-11 19:27 UTC (permalink / raw) To: Jon Turney, cygwin-apps 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-06-11 19:27 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <CAMxuvawMKvGwXcv4cCpSd4pgmwuqUjvy6UeSa6viKO-OF3dp3w@mail.gmail.com> 2022-02-28 13:29 ` Updating glib2 in cygwin Ken Brown 2023-06-11 17:55 ` Jon Turney 2023-06-11 19:27 ` Ken Brown
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).