From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: 75268@debbugs.gnu.org
Cc: andrew@trop.in, cox.katherine.e+guix@gmail.com,
liliana.prikler@gmail.com
Subject: [bug#75268] [PATCH emacs-team 2/2] gnu: emacs-next: Pin natively compiled packages.
Date: Wed, 1 Jan 2025 22:16:19 +0100 [thread overview]
Message-ID: <5b659b8ece40e2fe6e111190ed89029c84ac8dbb.1735766271.git.liliana.prikler@gmail.com> (raw)
In-Reply-To: <cover.1735766271.git.liliana.prikler@gmail.com>
* gnu/packages/emacs.scm (emacs)[patches]: Add
“emacs-native-comp-pin-packages.patch”.
---
gnu/packages/emacs.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index 7ce70de5c0f..b5c76586f7c 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu/packages/emacs.scm
@@ -578,6 +578,7 @@ (define-public emacs-next-minimal
"emacs-fix-scheme-indent-function.patch"
"emacs-next-native-comp-driver-options.patch"
"emacs-next-native-comp-fix-filenames.patch"
+ "emacs-native-comp-pin-packages.patch"
"emacs-pgtk-super-key-fix.patch")))))))
(define* (emacs->emacs-next emacs #:optional name
--
2.47.1
next prev parent reply other threads:[~2025-01-01 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 21:17 [bug#75268] [PATCH emacs-team 0/2] Apply native-comp grafts to emacs-next as well Liliana Marie Prikler
2025-01-01 21:15 ` [bug#75268] [PATCH emacs-team 1/2] gnu: emacs-next: Don't hash file names in native compilation Liliana Marie Prikler
2025-01-01 21:15 ` [bug#75268] [PATCH emacs-team v2 1/3] " Liliana Marie Prikler
2025-01-01 21:16 ` [bug#75268] [PATCH emacs-team v2 2/3] gnu: emacs-next: Pin natively compiled packages Liliana Marie Prikler
2025-01-06 16:31 ` [bug#75268] [PATCH emacs-team v2 3/3] gnu: emacs-next: Disable jit compilation Liliana Marie Prikler
2025-01-01 21:16 ` Liliana Marie Prikler [this message]
2025-01-08 4:48 ` [bug#75268] [PATCH emacs-team 0/2] Apply native-comp grafts to emacs-next as well Ian Eure
2025-01-08 5:16 ` 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=5b659b8ece40e2fe6e111190ed89029c84ac8dbb.1735766271.git.liliana.prikler@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=75268@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@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).