unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Mekeor Melire <mekeor@posteo.de>
Cc: 63984-done@debbugs.gnu.org, andrew@trop.in
Subject: bug#63984: [PATCH emacs-team 0/2] Start preparing for Emacs 29
Date: Thu, 13 Jul 2023 18:20:48 +0200	[thread overview]
Message-ID: <51a51d718a99a5160601517f22031b9ebe616f85.camel@gmail.com> (raw)
In-Reply-To: <87a5w1gfmp.fsf@posteo.de>

Am Mittwoch, dem 12.07.2023 um 18:15 +0000 schrieb Mekeor Melire:
> 2023-07-08 19:04 liliana.prikler@gmail.com:
> 
> > Am Dienstag, dem 04.07.2023 um 07:39 +0000 schrieb Mekeor 
> > Melire:
> 
> > > Why don't we build emacs-minimal with the configure-flag 
> > > --with-native-compilation=aot? If I understand correctly, this 
> > > would compile all .el-files of emacs-packages to .eln-files by 
> > > default. If I understand correctly, this currently only 
> > > happens for emacs-packages that use (arguments (#:emacs 
> > > emacs)).
> 
> > There's no point in using emacs-minimal for native-comp. It 
> > would just blow up our package sizes for no gain (any other 
> > emacs won't read the natively compiled elisp stuff due to having 
> > a different hash). If you have a use case for natively compiled 
> > emacs-minimal (e.g. for editing stuff on a server that should 
> > only carry small packages), I think there are better options 
> > (possibly emacs-no-x or using a "transformed" package).
> 
> Sorry. I think my suggestion was wrong and also I should submit it as
> a separate discussion. I'll send it to guix-devel. Stay tuned.
Possibly unrelated, but since we have 29.0.92 on master by now I pushed
this series and followed up with a merge.

Cheers





      reply	other threads:[~2023-07-13 16:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 16:22 [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29 Liliana Marie Prikler
2023-06-09  8:40 ` [bug#63984] [PATCH emacs-team 1/2] gnu: Make emacs-next-tree-sitter the new emacs Liliana Marie Prikler
2023-06-09 11:28   ` [bug#63984] [PATCH emacs-team 2/2] gnu: Construct Emacs packages from bottom up Liliana Marie Prikler
2023-06-10  6:46 ` [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29 Andrew Tropin
2023-06-10  7:46   ` Liliana Marie Prikler
2023-06-10  8:20     ` Andrew Tropin
2023-06-10  8:51       ` Liliana Marie Prikler
2023-06-11  5:35         ` Andrew Tropin
2023-06-11 21:09           ` Mekeor Melire
2023-06-12  4:30             ` Andrew Tropin
2023-07-04  7:39 ` Mekeor Melire
2023-07-08 17:04   ` Liliana Marie Prikler
2023-07-12 18:15     ` Mekeor Melire
2023-07-13 16:20       ` Liliana Marie Prikler [this message]

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=51a51d718a99a5160601517f22031b9ebe616f85.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=63984-done@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=mekeor@posteo.de \
    /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).