From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Add a configure option for NATIVE_FULL_AOT?
Date: Thu, 19 Aug 2021 09:27:06 +0200 [thread overview]
Message-ID: <20210819072706.GD13517@tuxteam.de> (raw)
In-Reply-To: <83bl5t3obt.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]
On Thu, Aug 19, 2021 at 10:07:02AM +0300, Eli Zaretskii wrote:
> > From: Richard Stallman <rms@gnu.org>
> > Cc: tsdh@gnu.org, emacs-devel@gnu.org
> > Date: Wed, 18 Aug 2021 22:34:10 -0400
> >
> > That's not what I said or meant. What I meant was that considering
> > the problem non-existent because this is how distros install the Lisp
> > files sounds strange to me, because it assumes no user will ever want
> > to modify these files enough to make them writable. IOW, the
> > assumption that bothered me was that no one will ever want to modify
> > those files, e.g., to fix some bug or add a feature.
> >
> > Distros must provide a way to download the sources. You could
> > download the sources into your home directory, make your modified
> > versions, and put them in a directory in load-path.
> >
> > Does this solve the problem, in practical terms?
>
> Not the problem I was describing, it doesn't.
>
> The problem I was describing was with the user modifying the *.el
> files installed by a distro. (The fact that distros by default
> install *.el files in a place that is generally not writable by users
> is irrelevant, because they can be made writable, or the *.el files
> can be copied to a writable location and modified there.) When users
> do modify the *.el files, the corresponding distributed *.eln files
> will no longer be loaded by Emacs, and there will be another version
> of those *.eln files in a different location. That is a gate to the
> "DLL hell" in its Emacs incarnation: several different shared-library
> objects of the same name in different locations. At the very least,
> users will be confused, and several obscure problems could happen that
> will be hard to debug. For example, the user's eln-cache directory,
> where the updated *.eln files will be stored, could be cleaned up by
> the user, not knowing that by doing that he/she effectively reverts to
> using the old code, triggers JIT compilation when he/she loads the
> same file the next time, etc. Not a catastrophe, but certainly
> confusing and not expected.
Sometimes, questions just have to be put by somewhere else. Now
I understand your position better :-)
I agree that this problem hasn't a trivial (or unique) solution.
But this is something for distros to solve. Emacs has just to
provide the mechanisms to make that possible (and, as far as I
can see, it does).
Note that this problem already exists with .el/.elc files.
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2021-08-19 7:27 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 8:53 Add a configure option for NATIVE_FULL_AOT? Ulrich Mueller
2021-08-17 11:42 ` Eli Zaretskii
2021-08-17 11:56 ` Ulrich Mueller
2021-08-17 12:09 ` Lars Ingebrigtsen
2021-08-17 13:03 ` Eli Zaretskii
2021-08-18 14:44 ` Lars Ingebrigtsen
2021-08-17 12:53 ` Eli Zaretskii
2021-08-17 13:07 ` Arthur Miller
2021-08-17 15:32 ` Yuri D'Elia
2021-08-17 17:01 ` Eli Zaretskii
2021-08-17 17:12 ` Yuri D'Elia
2021-08-17 18:19 ` Eli Zaretskii
2021-08-17 18:33 ` Andreas Schwab
2021-08-17 18:42 ` Eli Zaretskii
2021-08-17 18:46 ` Andreas Schwab
2021-08-17 19:01 ` Eli Zaretskii
2021-08-17 19:05 ` Andreas Schwab
2021-08-17 19:09 ` Eli Zaretskii
2021-08-17 19:36 ` Ulrich Mueller
2021-08-18 0:48 ` Arthur Miller
2021-08-18 7:29 ` Andreas Schwab
2021-08-18 15:43 ` Yuri D'Elia
2021-08-19 0:57 ` Arthur Miller
2021-08-19 7:04 ` tomas
2021-08-19 21:17 ` Arthur Miller
2021-08-20 7:20 ` tomas
2021-08-20 12:06 ` Arthur Miller
2021-08-20 13:13 ` tomas
2021-08-20 19:51 ` Arthur Miller
2021-08-20 20:06 ` tomas
2021-08-20 21:25 ` Arthur Miller
2021-08-21 6:44 ` tomas
2021-08-21 18:20 ` Arthur Miller
2021-08-19 7:13 ` Eli Zaretskii
2021-08-19 21:01 ` Arthur Miller
2021-08-18 2:23 ` Eli Zaretskii
2021-08-18 4:53 ` Tassilo Horn
2021-08-18 12:07 ` Eli Zaretskii
2021-08-19 2:34 ` Richard Stallman
2021-08-19 6:30 ` tomas
2021-08-19 7:07 ` Eli Zaretskii
2021-08-19 7:17 ` Andreas Schwab
2021-08-19 7:46 ` Eli Zaretskii
2021-08-19 7:27 ` tomas [this message]
2021-08-19 8:09 ` Eli Zaretskii
2021-08-19 10:05 ` tomas
2021-08-19 10:51 ` Eli Zaretskii
2021-08-19 12:49 ` tomas
2021-08-19 12:52 ` Eli Zaretskii
2021-08-19 13:09 ` tomas
2021-08-18 7:04 ` Ulrich Mueller
2021-08-18 12:12 ` Eli Zaretskii
2021-08-18 7:33 ` tomas
2021-08-18 12:14 ` Eli Zaretskii
2021-08-18 13:32 ` tomas
2021-08-18 13:45 ` Eli Zaretskii
2021-08-18 16:22 ` tomas
2021-08-18 16:26 ` Eli Zaretskii
2021-08-18 16:34 ` tomas
2021-08-18 16:43 ` Eli Zaretskii
2021-08-18 16:56 ` tomas
2021-08-18 17:12 ` Eli Zaretskii
2021-08-18 16:48 ` Stefan Monnier
2021-08-18 17:00 ` tomas
2021-08-18 17:17 ` Eli Zaretskii
2021-08-18 17:34 ` tomas
2021-08-18 19:43 ` Andrea Corallo via Emacs development discussions.
2021-08-19 1:19 ` Stefan Monnier
2021-08-19 7:11 ` Eli Zaretskii
2021-08-19 8:01 ` Andrea Corallo via Emacs development discussions.
2021-08-18 17:04 ` Eli Zaretskii
2021-08-18 19:44 ` Andrea Corallo via Emacs development discussions.
2021-08-19 7:17 ` Eli Zaretskii
2021-08-19 7:52 ` Andrea Corallo via Emacs development discussions.
2021-08-18 14:11 ` Stefan Kangas
2021-08-18 15:54 ` Eli Zaretskii
2021-08-18 19:13 ` Gunnar Horrigmo
2021-08-18 19:24 ` Eli Zaretskii
2021-08-20 8:22 ` Gunnar Horrigmo
2021-08-20 10:47 ` Eli Zaretskii
2021-08-20 13:06 ` Gunnar Horrigmo
-- strict thread matches above, loose matches on Subject: below --
2021-08-17 16:03 Tom Gillespie
2021-08-17 17:13 ` Eli Zaretskii
2021-08-17 21:52 ` Tom Gillespie
2021-08-18 12:04 ` Eli Zaretskii
2021-08-18 0:33 ` Arthur Miller
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=20210819072706.GD13517@tuxteam.de \
--to=tomas@tuxteam.de \
--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 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.