From: brettg@posteo.net
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: bug-Guix <bug-guix-bounces+brettg=posteo.net@gnu.org>,
Bug guix <Bug-guix@gnu.org>
Subject: bug#38261: Recent changes to emacs build system
Date: Tue, 19 Nov 2019 22:32:29 +0100 [thread overview]
Message-ID: <3bb8ddae57a7890e08438eda424bad34@posteo.net> (raw)
In-Reply-To: <874kyzwo66.fsf@gmail.com>
On 19.11.2019 22:29, Maxim Cournoyer wrote:
> brettg@posteo.net writes:
>
> [...]
>
>> Thank you for your work Maxim, I think most of them are resolved
>> now. I do wonder about what prompted the change, though. Perhaps you
>> might share?
>>
>> Brett
>
> The main motivation was to gain the ability to install Emacs in a given
> profile and have it use the Elisp libraries installed in said profile
> (and only from that profile). Using a search path specification is the
> native Guix mechanism to find libraries for systems that mostly rely on
> the FHS and means it work consistently across profiles, environments,
> or
> other features supported by Guix.
>
> There was a discussion here about this change and some feedback in the
> two weeks it was published preceding its merge:
> https://lists.gnu.org/archive/html/help-guix/2019-11/msg00000.html.
>
> HTH!
>
> Maxim
Maxim, indeed it does! I guess I was out of the loop on that
conversation and it just took me by surprise! Thanks for your efforts.
Best,
Brett
prev parent reply other threads:[~2019-11-19 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 19:01 bug#38261: Recent changes to emacs build system brettg
2019-11-18 20:28 ` brettg
2019-11-18 20:33 ` brettg
2019-11-18 21:34 ` brettg
2019-11-19 0:27 ` brettg
2019-11-19 0:32 ` brettg
2019-11-19 1:58 ` brettg
2019-11-19 21:14 ` Maxim Cournoyer
2019-11-19 21:16 ` brettg
2019-11-19 21:29 ` Maxim Cournoyer
2019-11-19 21:32 ` brettg [this message]
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=3bb8ddae57a7890e08438eda424bad34@posteo.net \
--to=brettg@posteo.net \
--cc=Bug-guix@gnu.org \
--cc=bug-guix-bounces+brettg=posteo.net@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).