unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: John Soo <jsoo1@asu.edu>
Cc: guix-devel@gnu.org
Subject: Re: Fixing and maintenance of emacs-guix (guix.el)
Date: Fri, 13 Nov 2020 18:28:59 +0100	[thread overview]
Message-ID: <87wnypb1yc.fsf@gnu.org> (raw)
In-Reply-To: <87sg9dxnvr.fsf@asu.edu> (John Soo's message of "Fri, 13 Nov 2020 07:44:24 -0800")

Hi John,

John Soo <jsoo1@asu.edu> skribis:

> I submitted https://gitlab.com/emacs-guix/emacs-guix/-/merge_requests/8
> to support guix versions >= 1.1.  However, two changes also have to
> occur for proper support.
>
> * Some bindings will need to be exposed on the guix side. I submitted
>   patches for this already: https://issues.guix.gnu.org/44619
>
> * The guix package in gnu/packages/package-management.scm will need to
>   refer to a commit including those patches.
>
> That leads to a more nebulous question: should there be "stable" and
> "unstable" versions of the guix package in guix?  Stable might be pinned
> to a release, but guix-unstable might be updated occasionally.

As I wrote in another message before reaching this one, my understanding
is that “we” now have to take over maintenance of Emacs-Guix.  As part
of that process, we can discuss what interfaces would be useful to
Emacs-Guix and arrange to keep them stable.

I think we can do more if the two are developed hand in hand.  Let’s see
what we can achieve!

Ludo’.


  reply	other threads:[~2020-11-13 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 15:44 Fixing and maintenance of emacs-guix (guix.el) John Soo
2020-11-13 17:28 ` Ludovic Courtès [this message]
2020-11-13 17:31   ` John Soo
2020-11-16  9:22     ` Ludovic Courtès
2020-11-13 18:54 ` zimoun
2020-11-14 10:39   ` Pierre Neidhardt

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=87wnypb1yc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jsoo1@asu.edu \
    /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).