From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Commit 958dd3ce68 will break emacs interface after "guix pull"
Date: Sun, 08 May 2016 18:04:18 +0200 [thread overview]
Message-ID: <87posw5yf1.fsf@gnu.org> (raw)
In-Reply-To: <87k2j7m4bm.fsf@gmail.com> (Alex Kost's message of "Fri, 06 May 2016 21:25:33 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2016-05-06 13:36 +0300) wrote:
[...]
>>> So I think it's the time to update guix-devel package. Is it OK to do
>>> it now?
>>
>> Yes, we could do that, but the problem remains on foreign distros
>> though.
>
> Not really: on foreign distros the recommended way (it's probably the
> only way except using git checkout) to use emacs interface is to install
> guix into a user profile, so once we update guix-devel snapshot, it can
> be updated by a user, and this breakage will be fixed.
At any rate, I’ll probably update it very soon.
>> What about simply #:re-export (memoize) in (guix utils) for now?
>
> Oh, indeed, this is a good workaround, thanks! OK for the attached
> patch or should I add some comment there?
[...]
> --- a/guix/utils.scm
> +++ b/guix/utils.scm
> @@ -44,6 +44,7 @@
> #:use-module (ice-9 format)
> #:use-module ((ice-9 iconv) #:select (bytevector->string))
> #:use-module (system foreign)
> + #:re-export (memoize)
Just add a comment there, like “for backwards compatibility”.
Thank you!
Ludo’.
next prev parent reply other threads:[~2016-05-08 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 21:51 System tests Ludovic Courtès
2016-05-05 9:27 ` Commit 958dd3ce68 will break emacs interface after "guix pull" Alex Kost
2016-05-06 10:36 ` Ludovic Courtès
2016-05-06 18:25 ` Alex Kost
2016-05-08 16:04 ` Ludovic Courtès [this message]
2016-05-09 8:43 ` Alex Kost
2016-06-21 8:56 ` System tests Ludovic Courtès
2016-06-22 21:33 ` Ludovic Courtès
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=87posw5yf1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
/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).