emacs-bug-tracker
[Top][All Lists]
Advanced

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

bug#44701: closed (28.0.50; [feature/native-comp] Use file-truename when


From: GNU bug Tracking System
Subject: bug#44701: closed (28.0.50; [feature/native-comp] Use file-truename when building eln path hash)
Date: Wed, 18 Nov 2020 20:58:01 +0000

Your message dated Wed, 18 Nov 2020 20:57:55 +0000
with message-id <xjfeekqbcx8.fsf@sdf.org>
and subject line Re: bug#44701: 28.0.50; [feature/native-comp] Use 
file-truename when building eln path hash
has caused the debbugs.gnu.org bug report #44701,
regarding 28.0.50; [feature/native-comp] Use file-truename when building eln 
path hash
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44701: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44701
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 28.0.50; [feature/native-comp] Use file-truename when building eln path hash Date: Mon, 16 Nov 2020 20:03:15 -0800
It appears that `comp-el-to-eln-filename` uses `expand-file-name` to
determine the absolute filename to
hash. When the filename is a symlink, this results in a cache miss
depending on which path is loaded.

`file-truename' would be the equivalent to `(expand-file-name name
nil)`, except that it would resolve to a
single canonical path (in the absence of hardlinks, which is pathological).

If I may ask, what is the purpose behind the path component of the
hash? I would think a content hash
would suffice to disambiguate files in the .el<->.eln bijection.

Thanks,
Tad



--- End Message ---
--- Begin Message --- Subject: Re: bug#44701: 28.0.50; [feature/native-comp] Use file-truename when building eln path hash Date: Wed, 18 Nov 2020 20:57:55 +0000 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
Tad <tadfisher@gmail.com> writes:

> This makes it possible to load AOT-compiled .eln files from the Nix
> store, so thank you for implementing this change.

That's good to hear!  Thank you for reporting, closing.

  Andrea


--- End Message ---

reply via email to

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