public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Po Lu via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Hook for `_exit'
Date: Fri, 05 Aug 2022 10:47:35 +0200	[thread overview]
Message-ID: <87k07n13h4.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87bksz6q14.fsf@yahoo.com> (Po Lu's message of "Fri, 05 Aug 2022 16:41:27 +0800")

* Po Lu:

> Florian Weimer <fweimer@redhat.com> writes:
>
>> It sounds like a bad idea to adopt a library that is already in
>> maintenance mode.
>
> So far it's proven to be the only practical way of gaining native
> Wayland support, and will at least be supported for the foreseeable
> future (just without major changes.)

What about GTK 4?  It looks like GTK 4 uses the same code.

You should ask them to switch to exit in GTK 4, and maybe that change
can be backported, maintenance mode or not.

Given that, it seems very premature to seek a glibc-level solution.

Thanks,
Florian


  reply	other threads:[~2022-08-05  8:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87les389c6.fsf.ref@yahoo.com>
2022-08-05  6:59 ` Po Lu
2022-08-05  8:22   ` Florian Weimer
2022-08-05  8:35     ` Po Lu
2022-08-05  8:38       ` Florian Weimer
2022-08-05  8:41         ` Po Lu
2022-08-05  8:47           ` Florian Weimer [this message]
2022-08-05  8:59             ` Po Lu
2022-08-05  9:02               ` Florian Weimer
2022-08-05  9:55                 ` Cyril Hrubis
2022-08-05 10:52                 ` Po Lu
2022-08-05 17:43                   ` Paul Eggert
2022-08-05 19:20                     ` Szabolcs Nagy
2022-08-05 20:11                       ` Paul Eggert
2022-08-05 22:41                         ` Adhemerval Zanella
2022-08-06  1:37                     ` Po Lu
2022-08-06  8:23                       ` Paul Eggert
2022-08-05 19:17     ` Rich Felker

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=87k07n13h4.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=luangruo@yahoo.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).