Re: Announcing emacs-guix-packaging

[zimoun <zimon.toutoune@gmail.com>]

Hi,

On Fri, 13 Nov 2020 at 10:45, Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> - Emacs-Guix uses private parts of Guix if I'm not mistaken.  Since
>   these parts are prone to change, it breaks Emacs-Guix once in a
>   while.

--8<---------------cut here---------------start------------->8---
$ ag '\(@' --scheme $(guix build emacs-guix -S)
/gnu/store/…-emacs-guix-0.5.2-2.58a840d-checkout/scheme/emacs-guix/actions.scm
200:            ((@@ (guix scripts build) log-url) store file))))))

/gnu/store/…-emacs-guix-0.5.2-2.58a840d-checkout/scheme/emacs-guix/system.scm
55:       ((@@ (gnu system) operating-system-firmware) os)))

/gnu/store/…-emacs-guix-0.5.2-2.58a840d-checkout/scheme/emacs-guix/pack.scm
31:  (map (@@ (guix scripts pack) compressor-name)
32:       (@@ (guix scripts pack) %compressors)))
40:              (@@ (guix scripts pack) %formats)))

/gnu/store/…-emacs-guix-0.5.2-2.58a840d-checkout/scheme/emacs-guix/profiles.scm
123:  (@@ (guix scripts package) search-path-environment-variables))
--8<---------------cut here---------------end--------------->8---

On the other hand, we could ask if these should not be part of the API.
The “(guix scrip <foo>)” seems a good clue. ;-)

From my point of view, your concern is not a real issue here.


> On the other hand, leveraging the actual Guix API is a saner approach
> than parsing the output.
>
> It's what I did in Nyxt:
>
> https://github.com/atlas-engineer/nyxt/blob/2-pre-release-4/libraries/ospama/ospama-guix.lisp

Nice trick!

But using “guix repl” is just a way to avoid to the binding Scheme-Emacs
(or -Common) Lisp, for instance avoid Geiser.  IIUC.

Well, maybe invoking “guix repl” is the fastest way to write plumbing
interfaces avoiding the tough binding.


All the best,
simon