From: Zhu Zihao <all_but_last@163.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53648@debbugs.gnu.org
Subject: [bug#53648] [PATCH] gnu: fcitx5-gtk: Add GTK 4 support.
Date: Mon, 07 Feb 2022 12:25:14 +0800 [thread overview]
Message-ID: <86czjz8fmt.fsf@163.com> (raw)
In-Reply-To: <cf67ecebe5ab6c9f8583204b349581fbbb85e807.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]
Maxime Devos <maximedevos@telenet.be> writes:
> [[PGP Signed Part:Undecided]]
> Zhu Zihao schreef op ma 07-02-2022 om 00:02 [+0800]:
>> Maxime Devos <maximedevos@telenet.be> writes:
>>
>> > What's the point of building for three separate gtk versions?
>> > Why not just build for gtk@4?
>>
>> Many packages still use GTK3, aren't they?
>>
>> > Also, if we go for multiple outputs, shouldn't the latest gtk
>> version
>> > go into "out" instead of the middle version gtk@3?
>>
>> IMO, GTK3 is still majority, so put it under "out", and make gtk2 and
>> gtk4 separated.
>
> It doesn't seem relevant to me that most packages use gtk+@3,
> since fcitx5-gtk is not most packages. Majority is irrelevant here.
>
> Anyways, we try to use the latest version of packages in Guix whenever
> feasible (for features, for bugfixes, because eventually the old
> versions will be unsupported upstream and to have less versions to
> keep track of), and gtk@4 is the latest version of gtk, so it seems to
> me that we should simplify things here by just using the latest version
> of gtk, i.e., gtk@4.
>
> Greetings,
> Maximes
>
> [[End of PGP Signed Part]]
It matters, because fcitx5-gtk is not a GTK *application*, it provides
IM module for GTK applications. Guix users may have both GTK3 & GTK4
application in same environment. If we drop gtk3 (or even gtk2), their
input method will be broken.
I just check the comment left by iyzsong, and I think it's better to
make the glib client in "out", and make IM module for different GTK
version in "gtk2" "gtk3" "gtk4" output. Thoughts?
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-02-07 4:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 6:53 [bug#53648] [PATCH] gnu: fcitx5-gtk: Add GTK 4 support Zhu Zihao
2022-02-06 12:47 ` Zhu Zihao
2022-02-06 15:48 ` Maxime Devos
2022-02-06 16:02 ` Zhu Zihao
2022-02-06 17:03 ` Maxime Devos
2022-02-07 4:25 ` Zhu Zihao [this message]
2022-02-07 8:42 ` Maxime Devos
2022-02-08 4:19 ` Zhu Zihao
2022-02-08 10:02 ` Maxime Devos
2022-02-09 2:12 ` Zhu Zihao
2022-02-09 11:05 ` Maxime Devos
2022-02-09 15:54 ` Zhu Zihao
2022-02-09 20:33 ` Maxime Devos
2022-02-09 23:23 ` Zhu Zihao
2022-02-11 17:42 ` Zhu Zihao
2022-02-14 13:36 ` Ludovic Courtès
2022-02-16 13:25 ` Zhu Zihao
2022-02-07 5:58 ` Zhu Zihao
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=86czjz8fmt.fsf@163.com \
--to=all_but_last@163.com \
--cc=53648@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.