From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: sha256: base32 VS nix-base32 Date: Sun, 09 Sep 2018 12:26:57 +0200 Message-ID: <87tvmzc6fi.fsf@gnu.org> References: <4537179.Lupmsyrybr@aleksandar-ixtreme-m5740> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41340) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fyx1R-0006tF-Fh for help-guix@gnu.org; Sun, 09 Sep 2018 06:32:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fywvl-0000to-Gr for help-guix@gnu.org; Sun, 09 Sep 2018 06:27:02 -0400 In-Reply-To: <4537179.Lupmsyrybr@aleksandar-ixtreme-m5740> (HiPhish's message of "Wed, 05 Sep 2018 17:35:30 +0200") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: HiPhish Cc: help-guix@gnu.org Hi, HiPhish skribis: > When using `guix download` and `guix hash` there are (among other) the fo= rmats=20 > `nix-base32` and `base32`. It appears that when writing a package definit= ion I=20 > have to use the former with the `(base32 "...")` expression. This really= =20 > confused be because I thought that "base32" means "base32" on both sides.= What=20 > is the deal with this? Package definitions expect a nix-base32-formatted string, even though the macro is called =E2=80=98base32=E2=80=99 and not =E2=80=98nix-base32=E2= =80=99. Internally Guix uses =E2=80=98nix-base32=E2=80=99 exclusively so you shouldn=E2=80=99t have to w= orry about it. HTH, Ludo=E2=80=99.