From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: ali_gnu2@emvision.com, emacs-devel@gnu.org
Subject: Re: Solaris dldump
Date: Mon, 19 Aug 2024 13:35:42 -0700 [thread overview]
Message-ID: <CADwFkmnDJLjS0P3NdN8XMtgnZwaV-QZ+Wc6gwLse26itgf=g2Q@mail.gmail.com> (raw)
In-Reply-To: <87h6bhgzc2.fsf@yahoo.com>
Po Lu <luangruo@yahoo.com> writes:
> Fedora 40's remaining support period is shorter; should we not cease to
> support it any longer,
We seem to be miscommunicating. I'm not suggesting explicitly
desupporting Solaris 10.
Spending considerable time on keeping the unexec build alive has stopped
making sense for the project as a whole. The good news is that there is
nothing to suggest that the portable dumper should not be fixable on the
systems where it's reportedly not yet up to scratch.
I'm saying 1) that the reported problems with the portable dumper on
some proprietary systems (MS-DOS, Windows 98, Solaris 10) should be
fixed, 2) that I do not consider this blocking us from dropping the
unexec build at the present time, and 3) I urged volunteers to step
forward to improve and/or fix pdumper on these systems.
I recommend reading the "Information for Maintainers of GNU Software"
manual to get a better view of some of the principles that are guiding
my thinking:
https://www.gnu.org/prep/maintain/maintain.html#Platforms
Note in particular this part:
"Supporting other platforms is optional -- we do it when that seems
like a good idea, but we don’t consider it obligatory. If the users
don’t take care of a certain platform, you may have to desupport it
unless and until users come forward to help. Conversely, if a user
offers changes to support an additional platform, you will probably
want to install them, but you don’t have to. If you feel the
changes are complex and ugly, if you think that they will increase
the burden of future maintenance, you can and should reject them.
This includes both free or mainly-free platforms such as OpenBSD,
FreeBSD, and NetBSD, and nonfree platforms such as Windows."
These are the basics, applicable to the GNU project as a whole. There
are special considerations for Emacs, of course, some of which have been
indicated in this thread. For example, we are probably "best-in-class"
among GNU projects when it comes to supporting various platforms, even
very old/obsolete ones, and at the cost of valuable time and resources.
So don't let anyone believe that we rush to leave (even fringe) groups
of users behind for no good reason. That's just not the case. But we
do have certain things that we prioritize ahead of others. That
sometimes means asking for volunteer help to do things that are merely
secondary, if that helps us advance our primary goals.
Right now, it's very clear that the unexec build has reached the end of
the road. Thus, we must ask volunteers to help us improve pdumper on
systems that, with respect to existing users, are not currently primary
considerations.
I hope that helps make things more clear.
> In any event, I promised to devote some of it to this issue after
> Emacs 30 is released.
That is good and welcome. Thanks in advance for your efforts.
prev parent reply other threads:[~2024-08-19 20:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.39.1723910423.12184.emacs-devel@gnu.org>
2024-08-17 22:49 ` Emacs-devel Digest, Vol 246, Issue 17 ali_gnu2
2024-08-18 0:10 ` Po Lu
2024-08-18 0:19 ` Po Lu
2024-08-18 1:15 ` Solaris dldump (was: Pure space) ali_gnu2
2024-08-18 1:25 ` Solaris dldump Po Lu
2024-08-18 22:27 ` Stefan Kangas
2024-08-18 23:56 ` Po Lu
2024-08-19 11:18 ` Eli Zaretskii
2024-08-19 12:09 ` Po Lu
2024-08-19 12:50 ` Eli Zaretskii
2024-08-19 11:44 ` Pip Cet
2024-08-19 11:57 ` Po Lu
2024-08-19 12:10 ` Pip Cet
2024-08-19 12:55 ` Eli Zaretskii
2024-08-19 13:46 ` Pip Cet
2024-08-19 14:39 ` Eli Zaretskii
2024-08-19 15:26 ` Corwin Brust
2024-08-19 15:31 ` Corwin Brust
2024-08-19 20:51 ` Stefan Kangas
2024-08-19 20:35 ` Stefan Kangas [this message]
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='CADwFkmnDJLjS0P3NdN8XMtgnZwaV-QZ+Wc6gwLse26itgf=g2Q@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=ali_gnu2@emvision.com \
--cc=emacs-devel@gnu.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.
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).