all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>, Alex <agrambot@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Increase minimum required GTK versions?
Date: Mon, 8 Apr 2019 16:58:46 -0700	[thread overview]
Message-ID: <ddf9a446-6037-148e-6bfd-2909f29a18d4@cs.ucla.edu> (raw)
In-Reply-To: <ee36msh3sg.fsf@fencepost.gnu.org>

On 4/8/19 9:15 AM, Glenn Morris wrote:
> I also have no problem with
> dropping RHEL6 support in Emacs 27 if it makes maintenance significantly
> easier.)

That would be a bridge too far. Several of the servers in my school are
still running RHEL 6, and people build and install recently-released
software like Emacs on them.

Although I don't know of any servers at UCLA still running RHEL 5, my
department's main server is still running Solaris 10 (released 2005,
"Extended Support" through 2021) and current Emacs is still relevant on
that platform, at least to me. I don't doubt there are still people
running RHEL 5 (released 2005, "Extended Life Cycle support" through
2020) and I suspect it's possible that some of them might like to run
current Emacs.

Emacs and most other GNU packages still run on Solaris 10, and it would
feel odd for a GNU package like Emacs to support a mostly-proprietary
system like Solaris for longer than it supports a mostly-free system
like Red Hat. That being said, Emacs still supports Windows 95
(originally released 1995, "extended support" through 2001) so there is
a precedent for Emacs supporting an old proprietary platform better than
an old mostly-free platform.

How much easier is it to drop support for RHEL 5 now, as opposed to
doing it next year when Red Hat stops supporting it?




  reply	other threads:[~2019-04-08 23:58 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 [this message]
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

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

  git send-email \
    --in-reply-to=ddf9a446-6037-148e-6bfd-2909f29a18d4@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=agrambot@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.