From: Joshua Branson <jbranso@dismail.de>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: zimoun <zimon.toutoune@gmail.com>,
Leo Famulari <leo@famulari.name>, help-guix <help-guix@gnu.org>
Subject: Re: calculate hashes for a new packages
Date: Fri, 19 Mar 2021 09:09:35 -0400 [thread overview]
Message-ID: <87pmzvp9ww.fsf@dismail.de> (raw)
In-Reply-To: <fe2d2c0a-afd7-fc1b-cc0a-94dd4831a786@posteo.de> (Zelphir Kaltstahl's message of "Wed, 10 Mar 2021 22:00:41 +0100")
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
> Hello Zimoun!
>
> 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.
I personally use guix download https://path/to/tarball. That outputs
the hash for me. :) Please note that I have never added or fixed a
patch for guix.
>
> So it all depends on what I specify in my package description, about how GNU
> Guix is to retrieve my package.
>
> Regards,
> Zelphir
--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
next prev parent reply other threads:[~2021-03-19 13:10 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
2021-03-10 21:47 ` zimoun
2021-03-19 13:09 ` Joshua Branson [this message]
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=87pmzvp9ww.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
--cc=zelphirkaltstahl@posteo.de \
--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).