From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: indieterminacy <indieterminacy@libre.brussels>, jgart <jgart@dismail.de>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: How do I verify my hashes?
Date: Thu, 14 Jul 2022 11:52:36 +0300 [thread overview]
Message-ID: <867d4g13fv.fsf@susa.mail-host-address-is-not-set> (raw)
In-Reply-To: <aaef1d732224fd534010bb70d1b10dc9@libre.brussels>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
indieterminacy <indieterminacy@libre.brussels>
anaandika:
> On 10-07-2022 04:12, jgart wrote:
>> Hi Guixers,
>>
>> Today Bonface mentioned to me that I should be cloning my packages and
>> verifying the hashes with `git hash-object` or `git hash` iirc?
>>
>
> Bonface gives very cogent demonstrations of workflow, encourage him to
> do a screencast!
>
I want to start online packaging/lisp-y/emacs-y
hang-outs here in Nairobi packaging meet-up thing
where we have recorded BBB sessions. Perhaps you
may find those helpful.
>> Do others do this when packaging?
>>
>> My workflow currently is the lazy way:
>>
>> 1. I change the version in the package definition.
>>
>> 2. build the package
>>
>> 3. package blows up on stdout
>>
>> 4. I retrieve the hash and add it
>>
>> 5. profit!
>>
>> But how can I trust that computed hash?
>>
>> wdyt
>
> Im slowly moving up the value-chain with my usage of Emacs' Git
> porceline, Magit.
>
> IMHO, the ultimate experience would be for everything operating from
> Magit's interface - for the beneficence of Guix.
>
FWIW, Magit runs on "transient" and IIRC you can
add anything to that interface. It was built,
just like GNU Emacs, to be extensible.
--
(Life is like a pencil that will surely run out,
but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
(hkp://keys.gnupg.net))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
prev parent reply other threads:[~2022-07-14 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 2:12 How do I verify my hashes? jgart
2022-07-10 4:13 ` Vagrant Cascadian
2022-07-10 10:09 ` Csepp
2022-07-10 13:25 ` indieterminacy
2022-07-10 16:59 ` jgart
2022-07-14 8:52 ` Munyoki Kilyungi [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=867d4g13fv.fsf@susa.mail-host-address-is-not-set \
--to=me@bonfacemunyoki.com \
--cc=help-guix@gnu.org \
--cc=indieterminacy@libre.brussels \
--cc=jgart@dismail.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).