From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/4] Make Emacs find packages in "~/.guix-profile".
Date: Thu, 14 Jan 2016 11:46:22 +0300 [thread overview]
Message-ID: <87pox4tuox.fsf@gmail.com> (raw)
In-Reply-To: <87oacp60vx.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 13 Jan 2016 14:54:10 +0100")
Ludovic Courtès (2016-01-13 16:54 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Ludovic Courtès (2016-01-10 23:21 +0300) wrote:
>>
>>> Alex Kost <alezost@gmail.com> skribis:
>>>
>>>> So this is a full patchset to "teach" Emacs how to find emacs packages
>>>> installed with Guix. See conversation at
>>>> <http://lists.gnu.org/archive/html/guix-devel/2016-01/msg00164.html>.
>>>>
>>>> [PATCH 1/4] emacs: Make "guix-emacs.el" independent.
>>>> [PATCH 2/4] emacs: Move loading packages to "guix-emacs.el".
>>>> [PATCH 3/4] gnu: emacs: Find packages in "~/.guix-profile".
>>>> [PATCH 4/4] doc: Describe how Emacs packages are found.
>>>>
>>>> There is an important nuance: the 3rd patch MUST NOT be committed along
>>>> with the first 2 patches, because it will make our Emacs package use an
>>>> old source of 'guix' which does not contain the required changes. So I
>>>> think we should:
>>>>
>>>> 1. Push the patches 1 and 2.
>>>>
>>>> 2. Wait for the next update of the 'guix-devel' snapshot (last time it
>>>> was updated in November¹, so it will probably happen soon).
>>>>
>>>> 3. And finally push the patches 3 and 4.
>>>
>>> OK. Note that we can update ‘guix-devel’ whenever we want. So if you
>>> take care of pushing things, feel free to do it yourself!
>>
>> Great, but I see that you updated guix-devel snapshot several days ago.
>> Would it be OK to update it again so soon?
>
> Sure.
Or maybe would it be better to update ‘guix-devel’ after core-updates
will be merged (since it is going to be really soon)?
>> If yes, then I will gladly push this patchset and update guix-devel as
>> appropriate.
>
> OK!
Thanks!
--
Alex
next prev parent reply other threads:[~2016-01-14 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 16:55 [PATCH 0/4] Make Emacs find packages in "~/.guix-profile" Alex Kost
2016-01-06 16:55 ` [PATCH 1/4] emacs: Make "guix-emacs.el" independent Alex Kost
2016-01-10 20:23 ` Ludovic Courtès
2016-01-06 16:55 ` [PATCH 2/4] emacs: Move loading packages to "guix-emacs.el" Alex Kost
2016-01-10 20:23 ` Ludovic Courtès
2016-01-06 16:55 ` [PATCH 3/4] gnu: emacs: Find packages in "~/.guix-profile" Alex Kost
2016-01-10 20:28 ` Ludovic Courtès
2016-01-12 9:18 ` Alex Kost
2016-01-13 13:53 ` Ludovic Courtès
2016-01-06 16:55 ` [PATCH 4/4] doc: Describe how Emacs packages are found Alex Kost
2016-01-10 20:31 ` Ludovic Courtès
2016-01-10 20:21 ` [PATCH 0/4] Make Emacs find packages in "~/.guix-profile" Ludovic Courtès
2016-01-12 9:18 ` Alex Kost
2016-01-13 13:54 ` Ludovic Courtès
2016-01-14 8:46 ` Alex Kost [this message]
2016-01-14 13:37 ` Ludovic Courtès
2016-01-29 9:04 ` Alex Kost
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pox4tuox.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.