From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: ~/.guix-profile/manifest usage with "guix package -m [manifest]" / "guix pack -m [manifest]" etc.. Date: Sat, 29 Sep 2018 18:33:17 +0200 Message-ID: <87efdcxnzm.fsf@gnu.org> References: <87h8ic36ix.fsf@gnu.org> 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]:50110) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g6IBP-0007xp-PJ for guix-devel@gnu.org; Sat, 29 Sep 2018 12:33:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g6IBN-0003lu-5w for guix-devel@gnu.org; Sat, 29 Sep 2018 12:33:31 -0400 In-Reply-To: (YOANN P.'s message of "Thu, 27 Sep 2018 20:03:23 +0000") 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" To: YOANN P Cc: "guix-devel@gnu.org" Hello, YOANN P skribis: > No offense, but, even if didn't try too many times to understand Guile Sc= heme, even if i really love Guix, the last time i tried to contribute (http= ://git.savannah.gnu.org/cgit/guix.git/commit/?id=3D6e0efe8cd5c85e7b83808b46= 6c626484274def8d) I really was not comfortable with this new language and m= y brain found it hard to understand the indentation rules / closing parenth= esis for a first approach. > If i acquire the skills to add it before someone doing it instead of me, = i will submit it with pleasure, because i'm sure to be not the only one wit= h this need :) and will be a pleasure to support a project i want see grow= ing. Sure, no problem. :-) We all rely heavily on editor support for parenthesis matching and indentation. The =E2=80=98etc/indent-code.el=E2= =80=99 script that comes with Guix helps with the latter (see ). Now I understand it takes some time to get used to it! > Nb: not directly related to this discussion, but since my last commit, i = don't know if you already add it, but adding to your CI a build test for th= e packages with a custom store to be sure there is no hardcoded path to /gn= u will prevent this kind of errors. No we don=E2=80=99t have such tests, but it=E2=80=99s a good idea. Thanks, Ludo=E2=80=99.