From: ludo@gnu.org (Ludovic Courtès)
To: HiPhish <hiphish@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: sha256: base32 VS nix-base32
Date: Sun, 09 Sep 2018 12:26:57 +0200 [thread overview]
Message-ID: <87tvmzc6fi.fsf@gnu.org> (raw)
In-Reply-To: <4537179.Lupmsyrybr@aleksandar-ixtreme-m5740> (HiPhish's message of "Wed, 05 Sep 2018 17:35:30 +0200")
Hi,
HiPhish <hiphish@posteo.de> skribis:
> When using `guix download` and `guix hash` there are (among other) the formats
> `nix-base32` and `base32`. It appears that when writing a package definition I
> have to use the former with the `(base32 "...")` expression. This really
> confused be because I thought that "base32" means "base32" on both sides. What
> is the deal with this?
Package definitions expect a nix-base32-formatted string, even though
the macro is called ‘base32’ and not ‘nix-base32’. Internally Guix uses
‘nix-base32’ exclusively so you shouldn’t have to worry about it.
HTH,
Ludo’.
next prev parent reply other threads:[~2018-09-09 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 15:35 sha256: base32 VS nix-base32 HiPhish
2018-09-09 10:26 ` Ludovic Courtès [this message]
2018-09-09 10:34 ` HiPhish
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=87tvmzc6fi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=hiphish@posteo.de \
/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.
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).