emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suppressing native compilation (short and long term)


From: Eli Zaretskii
Subject: Re: Suppressing native compilation (short and long term)
Date: Mon, 17 Oct 2022 20:07:57 +0300

> From: Liliana Marie Prikler <liliana.prikler@gmail.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>, 
>       rlb@defaultvalue.org, emacs-devel@gnu.org
> Date: Mon, 17 Oct 2022 18:59:11 +0200
> 
> > > > > I haven't followed the Guix part of this thread in detail, but
> > > > > I thought I'd just note that Emacs 29 now has the
> > > > > `inhibit-automatic-native-compilation' variable and and
> > > > > `EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION' environment
> > > > > variables, so this is implemented.
> > > > 
> > > > I thought this change was just into master "for discussion", are
> > > > we already suggesting users to integrate it in their
> > > > infrastructures? 
> > > > BTW AFAIU this usecase was already supported in 28 using
> > > > `native-comp-deferred-compilation'.
> > > The deferred-compilation switch still ends up writing to $HOME,
> > > which the new inhibit one doesn't.
> > 
> > I think Eli explained more than once how to avoid that also without
> > using the new switch.
> Now, I'm not following all branches of this discussion, so the chances
> that I missed something are admittedly high, but the last time I
> conversed with Eli about this, they said my use case was neither
> supported nor something they'd consider supporting.  Thus, I'd be
> positively surprised to see it in fact supported.

Which use case are you alluding to?

Andrea refers to preventing writes to user's HOME directory.  That
case is supported (in more than one way), and doesn't need the new
variable.  AFAIU, the use case you were presenting was not about
preventing writes to $HOME.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]