From: Suhail Singh <suhailsingh247@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: cox.katherine.e+guix@gmail.com, 72045@debbugs.gnu.org,
Suhail Singh <suhailsingh247@gmail.com>,
andrew@trop.in
Subject: bug#72045: [PATCH RFC 1/2] gnu: emacs: Compute ABI hash and native version dir without version.
Date: Sat, 13 Jul 2024 13:59:07 -0400 [thread overview]
Message-ID: <87msml41hw.fsf@gmail.com> (raw)
In-Reply-To: <4525ce8ef51ad9803a1d29da3c872080015b8b81.camel@gmail.com> (Liliana Marie Prikler's message of "Sat, 13 Jul 2024 19:26:10 +0200")
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> It could possibly allow us some flexibility in future changes, but at
> the very least it doesn't work right now. Hence why it's RFC while
> the other patch isn't.
Thank you for clarifying. It is clear that different versions of Emacs
store the natively compiled files in different locations. However, it's
less clear what happens during grafting and what is desired for grafting
and native compilation to work.
What is needed for grafting to work with native compilation? Is the
intent to be able to reuse the natively compiled files from the original
version when grafting installs the replacement version?
What happens during grafting today? Is the location where the original
version kept its natively compiled files kept around, or does it get
deleted when the replacement is grafted?
--
Suhail
next prev parent reply other threads:[~2024-07-13 18:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 20:06 bug#72045: Emacs graft lookup still fails Liliana Marie Prikler
2024-07-13 5:49 ` bug#72045: [PATCH RFC 1/2] gnu: emacs: Compute ABI hash and native version dir without version Liliana Marie Prikler
2024-07-13 5:53 ` bug#72045: [PATCH 2/2] gnu: emacs-minimal: Ungraft Liliana Marie Prikler
2024-07-13 16:14 ` Suhail Singh
2024-07-13 16:59 ` Liliana Marie Prikler
2024-07-13 16:08 ` bug#72045: [PATCH RFC 1/2] gnu: emacs: Compute ABI hash and native version dir without version Suhail Singh
2024-07-13 17:26 ` Liliana Marie Prikler
2024-07-13 17:59 ` Suhail Singh [this message]
2024-07-13 23:22 ` bug#72045: Emacs graft lookup still fails Suhail Singh
2024-07-14 8:50 ` Liliana Marie Prikler
2024-07-14 16:27 ` Suhail Singh
2024-07-14 16:46 ` Liliana Marie Prikler
2024-07-14 16:56 ` Suhail Singh
2024-07-14 16:59 ` Suhail Singh
2024-07-19 7:35 ` bug#72045: [PATCH v2 1/2] gnu: Add system test for Emacs Liliana Marie Prikler
2024-07-19 15:23 ` Suhail Singh
2024-07-19 15:42 ` Liliana Marie Prikler
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87msml41hw.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=72045@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=liliana.prikler@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).