Re: Finalizing 'inhibit-automatic-native-compilation'

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org,  akrl@sdf.org,  larsi@gnus.org,  rlb@defaultvalue.org
> Date: Sun, 29 Jan 2023 09:58:26 -0500
> 
> > IMO, the "no writable eln-cache" scenario should be solved by tweaking
> > native-comp-eln-load-path to include a writable directory.  That
> > writable directory could be temporary-file-directory, or it could be
> > anything else, but it should be specified by the caller/user, not
> > pulled out of our hat behind the scenes.
> 
> That's where I disagree: when it comes to trampolines I think users
> would be better served if we silently used an eln-cache in
> `temporary-file-directory` rather than ignoring the subr's redefinition
> (usually due to an advice).

Why? in the Debian use case all they care about is that the file is
not written to HOME, and my proposal doesn't break that.  The
trampoline isn't needed in their scenario, so there's no reason to
generate it.