From: Kaushal Modi <kaushal.modi@gmail.com>
To: Alex <agrambot@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Increase minimum required GTK versions?
Date: Mon, 8 Apr 2019 12:03:06 -0400 [thread overview]
Message-ID: <CAFyQvY1GAPcB6W-C6aZWQWoRy7fMw08FWrgQfBbBSpRcCfnxDw@mail.gmail.com> (raw)
In-Reply-To: <87y34kiloy.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On Mon, Apr 8, 2019 at 11:05 AM Alex <agrambot@gmail.com> wrote:
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> > Alex wrote:
> >> Both Debian Jessie (oldstable) and Ubuntu 14.04LTS include GTK 2.24 and
> >> 3.10. Is that good enough?
> >
> > I also suggest looking at RHEL 5, since Red Hat says they'll support it
> until
> > 2020-11-30 (see <https://access.redhat.com/articles/2986371>).
>
> Do we really have to consider RHEL 5, considering that it's on "Extended
> Life Cycle Support"[1]? If someone is paying extra for post-Production
> support for a "retired"[1] enterprise distro from 2007, then I doubt
> that they or their users will be running the latest Emacs, especially a
> GTK build instead of terminal-only or another toolkit such as Lucid.
> Even if they are, they can probably install a later version of GTK as
> well, right?
>
> RHEL 5 also only has GCC 4.1.2; is this enough for Emacs?
>
> FWIW, RHEL 6, which is still in Production phase, has GTK 2.24.
>
> I've attached a patch that bumps both versions and removes obsolete
> cruft. Bumping the GTK2 version helps the most here.
>
> [1] https://access.redhat.com/solutions/690063
>
I am on RHEL 6.8 (work) and my GTK version is 2.24.23. So thanks for
keeping the min supported GTK version as 2.24.
[-- Attachment #2: Type: text/html, Size: 1950 bytes --]
next prev parent reply other threads:[~2019-04-08 16:03 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 [this message]
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
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=CAFyQvY1GAPcB6W-C6aZWQWoRy7fMw08FWrgQfBbBSpRcCfnxDw@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=agrambot@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).