From: "Pierre-Henry F." <contact@phfrohring.com>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: "help-guix\\\\@gnu.org" <help-guix@gnu.org>
Subject: Re: sha256 base32 value of a git checkout
Date: Sun, 17 May 2020 15:08:16 +0000 [thread overview]
Message-ID: <CKSSTcI4Dxl-txr_4XbhAGw0-kg8dqE0W6a12Lb2qYKWSDjOXbHBDVt3ASagtpNEC9VKy3aZm3aUnCOd7x56eNi3HGg11AHQZ0duMQiOt2g=@phfrohring.com> (raw)
In-Reply-To: <20200517164410.2c9f2d0f@pantherarch.localdomain>
It worked!
Thanks!
phf
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, May 17, 2020 2:14 PM, Reza Alizadeh Majd <r.majd@pantherx.org> wrote:
> On Sun, 17 May 2020 12:00:38 +0000
> "Pierre-Henry F." contact@phfrohring.com wrote:
>
> > Hello,
> > I'm trying my hand on defining a package.
> > I have a source defined as in:
> > (origin
> > (method git-fetch)
> > (uri "some/git/dir")
> > (commit "acommit")
> > (file-name "a_filename")
> > (sha256 (base32 "XXX")))
> > when origin resolves to an archive, guix download $url gives the
> > value of "XXX" but when using git-fetch... how to get the value of
> > "XXX" ?
> > Thanks,
> > phf
>
> Hi,
>
> you can calculate directory hash recusrsively using guix with this
> command:
>
> `guix hash -rx /path/to/directory`
>
>
> ------------------------------------------------------------------------------------------------------------------------
>
> Reza Alizadeh Majd
> PantherX Team
prev parent reply other threads:[~2020-05-17 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 12:00 sha256 base32 value of a git checkout Pierre-Henry F.
2020-05-17 12:14 ` Reza Alizadeh Majd
2020-05-17 15:08 ` Pierre-Henry F. [this message]
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='CKSSTcI4Dxl-txr_4XbhAGw0-kg8dqE0W6a12Lb2qYKWSDjOXbHBDVt3ASagtpNEC9VKy3aZm3aUnCOd7x56eNi3HGg11AHQZ0duMQiOt2g=@phfrohring.com' \
--to=contact@phfrohring.com \
--cc=help-guix@gnu.org \
--cc=r.majd@pantherx.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.
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).