From: Ken Brown <kbrown@cornell.edu>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: Updating glib2 in cygwin
Date: Mon, 28 Feb 2022 08:29:48 -0500 [thread overview]
Message-ID: <886be9ed-aa97-b624-c701-e66532f9a73a@cornell.edu> (raw)
In-Reply-To: <CAMxuvawMKvGwXcv4cCpSd4pgmwuqUjvy6UeSa6viKO-OF3dp3w@mail.gmail.com>
[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
next parent reply other threads:[~2022-02-28 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMxuvawMKvGwXcv4cCpSd4pgmwuqUjvy6UeSa6viKO-OF3dp3w@mail.gmail.com>
2022-02-28 13:29 ` Ken Brown [this message]
2023-06-11 17:55 ` Jon Turney
2023-06-11 19:27 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=886be9ed-aa97-b624-c701-e66532f9a73a@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
--cc=marcandre.lureau@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).