From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [PATCH 0/4] Make Emacs find packages in "~/.guix-profile". Date: Thu, 14 Jan 2016 14:37:01 +0100 Message-ID: <87y4bsqo3m.fsf@gnu.org> References: <1452099305-746-1-git-send-email-alezost@gmail.com> <8737u55gnz.fsf@gnu.org> <874mejm9zv.fsf@gmail.com> <87oacp60vx.fsf@gnu.org> <87pox4tuox.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33203) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aJi5L-0007gX-Lv for guix-devel@gnu.org; Thu, 14 Jan 2016 08:37:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aJi5I-0000fF-DT for guix-devel@gnu.org; Thu, 14 Jan 2016 08:37:07 -0500 In-Reply-To: <87pox4tuox.fsf@gmail.com> (Alex Kost's message of "Thu, 14 Jan 2016 11:46:22 +0300") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Alex Kost Cc: guix-devel@gnu.org Alex Kost skribis: > Ludovic Court=C3=A8s (2016-01-13 16:54 +0300) wrote: > >> Alex Kost skribis: >> >>> Ludovic Court=C3=A8s (2016-01-10 23:21 +0300) wrote: >>> >>>> Alex Kost skribis: >>>> >>>>> So this is a full patchset to "teach" Emacs how to find emacs packages >>>>> installed with Guix. See conversation at >>>>> . >>>>> >>>>> [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 alo= ng >>>>> 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=C2=B9, so it will probably happen soon). >>>>> >>>>> 3. And finally push the patches 3 and 4. >>>> >>>> OK. Note that we can update =E2=80=98guix-devel=E2=80=99 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 =E2=80=98guix-devel=E2=80=99 after = core-updates > will be merged (since it is going to be really soon)? Either way is fine. (Note that it takes several days to build everything, not counting things we might need to fix in the middle.) Ludo=E2=80=99.