From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 21127@debbugs.gnu.org, Mathieu Lirzin <mthl@openmailbox.org>
Subject: bug#21127: Problem with guix.el on hybrid systems.
Date: Sat, 25 Jul 2015 10:52:17 +0300 [thread overview]
Message-ID: <87fv4c3c9a.fsf@gmail.com> (raw)
In-Reply-To: <87h9otfgbs.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 24 Jul 2015 22:31:19 +0200")
Ludovic Courtès (2015-07-24 23:31 +0300) wrote:
> Mathieu Lirzin <mthl@openmailbox.org> skribis:
>
>> From ca4360cc33f56dbfd1fa1367f68d3bd3d0d7c553 Mon Sep 17 00:00:00 2001
>> From: Mathieu Lirzin <mthl@openmailbox.org>
>> Date: Fri, 24 Jul 2015 12:59:20 +0200
>> Subject: [PATCH] emacs: Fix guix-guile-program.
>>
>> * emacs/guix-backend.el: Move to ...
>> * emacs/guix-backend.el.in: ... here.
>> (guix-guile-program): Default to the Guile used when building Guix to
>> avoid breaking guix.el when installing another Guile.
>> * configure.ac: Adapt to it.
>> * .gitignore: Likewise.
>
> [...]
>
>> +(defvar guix-guile-program "@GUILE@"
>
> Sounds reasonable to me.
>
> Alternately, I wonder if it would make sense to define that variable in
> guix-init.el to avoid having an additional .in file.
>
> Alex, WDYT?
Mathieu, thanks for catching it! I also think that it is better to
avoid converting "guix-backend.el" into ".in" file.
I had the same question with 'guix-load-path' variable when Emacs UI was
merging into Guix: this var was defined in "guix-backend.el" but it had
to depend on @prefix@, so I just put another "(defvar …)" into
"guix-init.el.in". As you can see there are 2 definitions of
'guix-load-path':
- in "guix-backend.el" (with an old "configure"-independent value)
- and in "guix-init.el" (with the current default value).
So I suggest to do the same with 'guix-guile-program', i.e. to put
(defvar guix-guile-program "@GUILE" …)
into "guix-init.el.in" and that's it. Since "guix-init.el" is loaded
the first, "defvar" in "guix-backend.el" will not override the default
value.
--
Alex
next prev parent reply other threads:[~2015-07-25 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 12:25 bug#21127: Problem with guix.el on hybrid systems Mathieu Lirzin
2015-07-24 20:31 ` Ludovic Courtès
2015-07-25 7:52 ` Alex Kost [this message]
2015-09-11 17:26 ` 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=87fv4c3c9a.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=21127@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mthl@openmailbox.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).