Am Samstag, dem 17.08.2024 um 11:26 +0200 schrieb Tomas Volf: > On 2024-07-31 19:10:03 +0200, Liliana Marie Prikler wrote: > > The other (recommended at the moment) would be to use the proper > > transformation to natively compile your emacs packages. > > So just to make sure I understand correctly what is the correct work > around here. Let us assume I install emacs and emacs-magit into my > home environment. So until now I have (leaving everything else out) > this: > > (home-environment > (packages (list emacs emacs-magit <more-here>))) > > Assuming I want to follow the recommendation above, I should turn it > into something like this: > > (home-environment > (packages (map (package-input-rewriting `((,emacs-minimal . > ,emacs))) > (list emacs emacs-magit <more-here>)))) > > Did I get it right? Are there any downsides to doing this (except > compute)? Yep, that's the low-level way of achieving this (more or less – emacs- minimal isn't always the only package to replace). On a higher level, you can bind (package-input-rewriting …) to a name and use that. I personally prefer the (options->transformation …)¹ variant, though, which is nearly identical and compiles to this.
Cheers > Side note: I am surprised how long emacs-yaml takes to build on my > ~5.5 GHz build machine. I compile whole of firefox faster. That sounds concerning. We might want to look into individual bugs such as this. ¹ the argument is '((with-input . "emacs-minimal=<your-emacs>")), which imho, reads nicer. <your-emacs> could be emacs, emacs-pgtk, etc.
