unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: rms@gnu.org, 18205@debbugs.gnu.org
Subject: bug#18205: Obsolete patterns in auto-mode-alist
Date: Sat, 09 Aug 2014 14:53:43 +0300	[thread overview]
Message-ID: <83tx5llvzs.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdogA7RcHW94AjFgPSXiX3RihQ=stHuq0nZtTodc1eR2-Zg@mail.gmail.com>

> Date: Sat, 9 Aug 2014 10:11:54 +0100
> From: Reuben Thomas <rrt@sc3d.org>
> Cc: Richard Stallman <rms@gnu.org>, Glenn Morris <rgm@gnu.org>, 18205@debbugs.gnu.org
> 
> > The current DJGPP build "just works", given that you have a correct
> > setup on a system that supports the build (requirements for supporting
> > the build might be different from those for supporting running of the
> > binary).
> 
> The trouble is that despite carefully-written and lengthy documentation,
> these requirements aren't fully documented

They are documented for systems that the people who wrote those
instructions had access to.  FreeDOS is not among them, so I don't
know if it complies.

> and yet it seems users are expected to build Emacs for themselves

Not "expected", "encouraged".

> So either that expectation should be changed (i.e. binary builds should be
> supplied in a timely fashion to the DJGPP site, and that sentence in the
> documentation changed), or the build instructions should be improved.

I supplied the 23.3 binary.  I intend to upload a 24.4 binary once it
is out.  Previous versions were IMO not stable enough to warrant an
upload.

As for improving the instructions, I don't know what to do about
that.  Once again, I have multiple success reports from people
building Emacs on various platforms that support DOS, and only one
failure report from you.  With all due respect, I don't think this is
a sign of inadequate instructions.

As I wrote earlier, if you are willing to continue building the DJGPP
port on FreeDOS on a more or less regular basis, I'm here to help you
debug whatever problems you originally had with your build.

> If people are still using Emacs on DOS, and they're expected to build it
> from source, surely this is not a waste of effort? Or, no-one is using it,
> and we should remove the port.

See above: there's a world between these 2 extremities.  Evidently,
people who have working DJGPP installations do succeed in building
Emacs, and there are still users who'd like to have newer binaries.

> > Given the above, investing efforts in moving DJGPP to the Posix
> > configury is a waste of resources that are best applied to parts of
> > Emacs that will benefit users of modern systems.
> >
> 
> FreeDOS is an active project, and it's free. It seems odd to me that we
> should be happy that Emacs builds on a defunct proprietary system, and not
> (apparently) on a closely-related, active, free one.

The DJGPP port of Emacs is currently supported by a single individual
-- yours truly.  I'm doing the minimum to keep the port alive, so that
I could invest most of my scarce free time to more broadly useful
Emacs tasks.  If you want to help in supporting the DJGPP port,
welcome aboard.  If not, I respectfully request that you trust me to
do the best I can in the little time I can afford devoting to this.
Currently, I don't plan to move my DJGPP development environment to
FreeDOS, I simply cannot afford such an effort (FreeDOS is
sufficiently different from MS-DOS and its other emulations to
necessitate a non-trivial effort).  I understand the theory behind the
urge to move to FreeDOS, but it will have to be done by someone else.





  reply	other threads:[~2014-08-09 11:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 23:58 bug#18205: Obsolete patterns in auto-mode-alist Reuben Thomas
2014-08-06 17:41 ` Stefan Monnier
2014-08-06 17:47   ` Reuben Thomas
2014-08-06 18:04     ` Eli Zaretskii
2014-08-07  0:14   ` Glenn Morris
2014-08-07  2:53     ` Eli Zaretskii
2014-08-07  9:39       ` Reuben Thomas
2014-08-07 10:07         ` Reuben Thomas
2014-08-07 10:18           ` Reuben Thomas
2014-08-07 18:24           ` Richard Stallman
2014-08-07 12:23         ` Stefan Monnier
2014-08-07 15:28           ` Eli Zaretskii
2014-08-07 19:12             ` Stefan Monnier
2014-08-07 19:40               ` Eli Zaretskii
2014-08-07 18:24       ` Richard Stallman
2014-08-07 19:34         ` Eli Zaretskii
2014-08-08  5:35           ` Richard Stallman
2014-08-08  6:06             ` Eli Zaretskii
2014-08-08 19:11               ` Richard Stallman
2014-08-08 20:09                 ` Eli Zaretskii
2014-08-08 20:54                 ` Reuben Thomas
2014-08-08 23:19               ` Reuben Thomas
2014-08-09  6:49                 ` Eli Zaretskii
2014-08-09  7:41                   ` Reuben Thomas
2014-08-09  7:44                   ` Reuben Thomas
2014-08-09  8:30                     ` Eli Zaretskii
2014-08-09  9:11                       ` Reuben Thomas
2014-08-09 11:53                         ` Eli Zaretskii [this message]
2014-08-09 11:57                           ` Reuben Thomas
2014-08-09 14:27                             ` Eli Zaretskii
2014-08-07  4:25   ` Richard Stallman
2014-08-06 18:01 ` Eli Zaretskii
2014-08-06 22:05   ` Reuben Thomas
2014-08-07  2:51     ` Eli Zaretskii
2014-08-07 12:02       ` Reuben Thomas
2014-08-07 15:27         ` Eli Zaretskii
2014-08-07 11:54     ` Reuben Thomas
2014-08-06 23:57 ` Glenn Morris

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=83tx5llvzs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18205@debbugs.gnu.org \
    --cc=rms@gnu.org \
    --cc=rrt@sc3d.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).