unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: zimoun <zimon.toutoune@gmail.com>, Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: calculate hashes for a new packages
Date: Wed, 10 Mar 2021 22:00:41 +0100	[thread overview]
Message-ID: <fe2d2c0a-afd7-fc1b-cc0a-94dd4831a786@posteo.de> (raw)
In-Reply-To: <86y2eubw2v.fsf@gmail.com>

Hello Zimoun!

On 3/10/21 9:19 PM, zimoun wrote:
> On Wed, 10 Mar 2021 at 14:21, Leo Famulari <leo@famulari.name> wrote:
>> On Wed, Mar 10, 2021 at 08:14:43PM +0100, Zelphir Kaltstahl wrote:
>>> How does one calculate the hash for a package one wants to add to GNU Guix?
>>>
>>> I know 2 ways, giving me different results. One is for the repository folder and
>>> one is for the tarball:
>>>
>>> ~~~~
>>> guix hash --exclude-vcs --recursive .
>>> guix hash PACKAGE-VERSION-tar.gz  # a tarball created by guile-hall
>> Can you clarify your question?
>>
>> It seems to me that you already know the answer: You use the method that
>> is appropriate for your package. It depends on what kind of source code
>> your packages uses.
> Concretely, url-fetch
>
>    guix hash PACKAGE-VERSION-tar.gz
>
> or git-fetch (or other vcs):
>
>    guix hash .
>
>
> Maybe the question could be clarified. :-)
>
>
> Cheers,
> simon

Ah, I think I get it now:

If I for example created a tag for the version of my package and creation of the
tag caused the VCS host to create a tarball as release, I could go the url-fetch
way and then I would use `guix hash` on the tarball, which is the release
tarball, but if there is no release tarball addressable using a URL, I would use
the git-fetch way, which means GNU Guix would have to verify the downloaded
repository, so I calculate the hash using the other way.

So it all depends on what I specify in my package description, about how GNU
Guix is to retrieve my package.

Regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl



  reply	other threads:[~2021-03-10 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 19:14 calculate hashes for a new packages Zelphir Kaltstahl
2021-03-10 19:21 ` Leo Famulari
2021-03-10 20:19   ` zimoun
2021-03-10 21:00     ` Zelphir Kaltstahl [this message]
2021-03-10 21:47       ` zimoun
2021-03-19 13:09       ` Joshua Branson
2021-03-10 20:22   ` Zelphir Kaltstahl
2021-03-10 21:11 ` divoplade

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=fe2d2c0a-afd7-fc1b-cc0a-94dd4831a786@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    --cc=zimon.toutoune@gmail.com \
    /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).