--- Begin Message ---
|
Subject: |
[PATCH emacs-team 0/2] Start preparing for Emacs 29 |
|
Date: |
Fri, 9 Jun 2023 18:22:07 +0200 |
Hi Guix,
it's already been four weeks since the newest Emacs pre-release. Time
sure flies. With that in mind, I'd like to start work in the Emacs team
focused on
1. streamlining our Emacs packages
2. improving emacs-build-system and adapting it to the new features of
Emacs 29 (including the almost forgotten [1])
3. improving our Emacs package management (i.e. making it easier to
declare variants of emacs-* packages built with different Emacsen)
This series gets us started on (1), so we can do (2) and (3) hopefully
soon.
Cheers
[1] https://issues.guix.gnu.org/57122
Liliana Marie Prikler (2):
gnu: Make emacs-next-tree-sitter the new emacs.
gnu: Construct Emacs packages from bottom up.
gnu/local.mk | 1 -
gnu/packages/emacs.scm | 467 +++++++-----------
.../patches/emacs-source-date-epoch.patch | 20 -
3 files changed, 190 insertions(+), 298 deletions(-)
delete mode 100644 gnu/packages/patches/emacs-source-date-epoch.patch
base-commit: 44bbfc24e4bcc48d0e3343cd3d83452721af8c36
--
2.40.1
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29 |
|
Date: |
Thu, 13 Jul 2023 18:20:48 +0200 |
|
User-agent: |
Evolution 3.46.4 |
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
--- End Message ---