Re: Add a configure option for NATIVE_FULL_AOT?

[Eli Zaretskii <eliz@gnu.org>]

> Date: Wed, 18 Aug 2021 18:56:53 +0200
> From: tomas@tuxteam.de
> Cc: emacs-devel@gnu.org
> 
> > > > Nominally, yes.  But then you have 2 copies of the same .eln file, in
> > > > 2 different places.
> > > 
> > > They would be different, one of them from an .el with user changes.
> > 
> > Sure, that's my point.
> 
> And we want the user's .el and the corresponding .eln to override
> the system-provided ones. So those (more precisely: their directories
> should go first in their corresponding paths, right?

They should go first in the list that is the value of
native-comp-eln-load-path, yes.

> > How would that precedence work, except by relying on the order of the
> > directories in the list?
> 
> I must have expressed my thoughts too clumsily. I do agree with you
> that the several paths are in order of descending preferences.
> 
> What I'm implying from that is that the place for the user's .eln
> files should be more at the front of this path, so the .jit mechanism
> should put them there, if they have to override the system-provided
> ones.

That's where they are, and that's where JIT compilation puts them.

But that is TRT for *.el files _other_ than the ones inside
/usr/lib/.../native-lisp/, since those other files are _always_
compiled into the user's eln-cache directory.  Thus we avoid the
danger of having several variants of the same .eln file with the same
name.  That doesn't work if the original .eln file is under /usr/lib.
And therein lies the problem I was trying to describe.