From: Eli Zaretskii <eliz@gnu.org>
To: Ali Bahrami <ali_gnu2@emvision.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Finding the dump (redux)
Date: Mon, 19 Apr 2021 20:19:56 +0300 [thread overview]
Message-ID: <837dkyry2r.fsf@gnu.org> (raw)
In-Reply-To: <efdece15-633a-5b40-3f60-0e8682b20370@emvision.com> (message from Ali Bahrami on Mon, 19 Apr 2021 10:39:17 -0600)
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> From: Ali Bahrami <ali_gnu2@emvision.com>
> Date: Mon, 19 Apr 2021 10:39:17 -0600
>
> > This has been considered back when the portable dumping ideas were
> > discussed. One reason why it was rejected is because it would require
> > end users to have a C development toolchain if they want to re-dump
> > Emacs (with some of their own code added). Support for re-dumping is
> > a goal in Emacs development, and although we are not there yet, doing
> > something that would prevent it is a non-starter. We want users to be
> > able to re-dump Emacs using just Emacs and nothing else.
> >
>
> Is it really a conflict? Can't we do both?
>
> We would still have support for putting a pdump file
> next to the binary, or of using the --dump-file option.
> We could even retain the PATH_EXEC support if that helped.
> I don't think we need to take anything away, in terms of
> re-dumping Emacs using just Emacs.
>
> What we'd be doing, is to provide the final default (backstop)
> dump internally, rather than on disk. If a dump is present through
> any other method, that one would be used. But if not, as I think would
> be the case for most emacs users who get it via some distro package,
> emacs would 'just work', without their having to even know about
> pdump. Most distros wouldn't ship any separate pdmp files, but
> end users could add what they want.
I don't understand: if the user re-dumps Emacs, then under your
suggestion the user will have the same problem with Emacs locating the
pdumper file as we have today. So what did we fix, exactly?
next prev parent reply other threads:[~2021-04-19 17:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 19:38 Finding the dump (redux) Ali Bahrami
2021-04-17 18:45 ` Eli Zaretskii
2021-04-18 0:15 ` Ali Bahrami
2021-04-18 7:55 ` Eli Zaretskii
2021-04-18 8:18 ` Andreas Schwab
2021-04-18 16:05 ` Glenn Morris
2021-04-19 4:53 ` Richard Stallman
2021-04-19 8:35 ` Andreas Schwab
2021-04-19 13:00 ` Eli Zaretskii
2021-04-19 13:04 ` Ali Bahrami
2021-04-19 13:14 ` Eli Zaretskii
2021-04-19 13:34 ` Stefan Kangas
2021-04-19 14:39 ` Eli Zaretskii
2021-04-19 15:41 ` Ali Bahrami
2021-04-19 15:58 ` Eli Zaretskii
2021-04-19 16:08 ` Ali Bahrami
2021-04-19 17:09 ` Eli Zaretskii
2021-04-19 4:01 ` Ali Bahrami
2021-04-19 13:26 ` Stefan Monnier
2021-04-19 14:28 ` Eli Zaretskii
2021-04-19 14:50 ` Stefan Monnier
2021-04-19 15:43 ` Ali Bahrami
2021-04-19 16:06 ` Eli Zaretskii
2021-04-19 16:39 ` Ali Bahrami
2021-04-19 17:19 ` Eli Zaretskii [this message]
2021-04-19 18:03 ` Ali Bahrami
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=837dkyry2r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ali_gnu2@emvision.com \
--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 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.