unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Increase minimum required GTK versions?
Date: Wed, 10 Apr 2019 18:57:47 +0300	[thread overview]
Message-ID: <83sgup6ef8.fsf@gnu.org> (raw)
In-Reply-To: <87h8b61rid.fsf@gmail.com> (message from Alex on Tue, 09 Apr 2019 21:14:02 -0600)

> From: Alex <agrambot@gmail.com>
> Cc: eggert@cs.ucla.edu,  monnier@iro.umontreal.ca,  emacs-devel@gnu.org
> Date: Tue, 09 Apr 2019 21:14:02 -0600
> 
> > To allow proper review, please make the log message more detailed.  In
> > particular, stuff you remove that is not under an explicit GTK version
> > condition should have a minimal explanation for why it is TRT to
> > remove it.  (The rationale doesn't have to be in the log message,
> > although it would be nice to have it there; it could be just in the
> > email that accompanies the patch.)
> 
> Here's a brief overview of the changes outside of explicit checks:

Thanks, I think most of this text should be in the commit log.  It's
not too long for that, and provides useful information.

> * Old file selection dialog
> This is only optionally used in GTK 2, but the old dialog is long
> deprecated in GTK 2 (removed in GTK 3), so I figured that this is a good
> time to remove it and simplify the existing code.

I think this should be left alone.  It's a separate issue anyway, and
should be submitted separately.  It would be good to try to establish
whether this feature is turned on by someone, but given that it's only
for GTK2, I tend to think we should simply let it die a natural death
together with GTK2.

> > Please also tell with which GTK versions did you try building with to
> > verify the correctness of the changes.
> 
> I tested with GTK 2.24.32 and GTK 3.24.7. I didn't see a need to test
> with an older GTK 3 version since the GTK 3 part of the change involves
> simplifying version checks 3 <= version <= 3.10 (and
> USE_NEW_GTK_FONT_CHOOSER) to HAVE_GTK3 checks.

I think it would be good to see if the changes compile with 3.10
nonetheless.  Can someone please try that?

> > Not sure we discussed 3.10 as the minimum GTK3 version, we only talked
> > about 2.x AFAIR.  What is the situation with GTK3 versions in the
> > current distributions of GNU/Linux?
> 
> My messages briefly discussed the minimum of 3.10 and how Debian Jessie
> (oldstable -- soon to be oldoldstable), and Ubuntu 14.04LTS have GTK 3.10.

What about others, like RH?

> RHEL doesn't even support GTK 3 until RHEL 7, which has 3.22.

AFAIK, Red Hat is not limited to RHEL, and then there are derivatives,
like CentOS.  (I'm not saying those others come with older GTK3, I'm
just saying we should check.)

> So I think bumping to 3.10 doesn't hurt, especially since there's still
> GTK 2 support.

It sounds to me a bit drastic to tell people to downgrade to GTK2
because we don't support old enough GTK3.

Thanks.



  reply	other threads:[~2019-04-10 15:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 19:03 Increase minimum required GTK versions? Alex
2019-04-07 19:08 ` Eli Zaretskii
2019-04-07 19:25   ` Alex
2019-04-08  4:45     ` Paul Eggert
2019-04-08 15:03       ` Alex
2019-04-08 16:03         ` Kaushal Modi
2019-04-08 16:15         ` Glenn Morris
2019-04-08 23:58           ` Paul Eggert
2019-04-09  1:55             ` Stefan Monnier
2019-04-09  4:47               ` Paul Eggert
2019-04-09 17:28                 ` Alex
2019-04-09 18:21                   ` Eli Zaretskii
2019-04-10  3:14                     ` Alex
2019-04-10 15:57                       ` Eli Zaretskii [this message]
2019-04-10 16:20                         ` Stefan Monnier
2019-04-10 16:43                           ` Eli Zaretskii
2019-04-11  0:35                         ` Alex
2019-04-11  1:26                           ` Alex Branham
2019-04-11 14:19                             ` Eli Zaretskii
2019-04-11 14:26                               ` Dmitry Gutov
2019-04-11 14:29                               ` Alex
2019-04-12 18:49                           ` Eli Zaretskii
2019-04-12 19:05                             ` Alex Gramiak
2019-04-12 19:14                               ` Eli Zaretskii
2019-04-12 19:33                                 ` Alex Gramiak
2019-04-12 19:45                                   ` Eli Zaretskii
2019-04-12 20:04                                     ` Alex Gramiak
2019-04-12 20:17                                       ` Eli Zaretskii
2019-04-09  5:00               ` Van L

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83sgup6ef8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=agrambot@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).