From: Stephen Paul Weber <singpolyma@singpolyma.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, 0@psycoti.ca
Subject: Re: git-fetch without a hash
Date: Tue, 3 Jan 2023 14:31:20 -0500 [thread overview]
Message-ID: <Y7SCiE9URY5K//zX@singpolyma-beefy.lan> (raw)
In-Reply-To: <87h6xo2wz8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
>> However, there's no real reason that git-fetch *needs* to be
>> fixed-output in terms of having a hash pre-defined, at least for local
>> development and other purposes. So is there a way around this?
>
> • write (package (source (git-checkout …)) …)
This works well. Now I'm curious how to know what can go in the (source)
field? Obviously not just (origin)...
>> If having a way around it is not desirable should url-fetch consider
>> this an error as well?
>
>I’m not sure; do you have an example where it’s not behaving as
>expected?
Yes. When using (sha256 #f) url-fetch still has network access and works to
download things, which is inconsistent vs other fetchers.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-03 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 3:04 git-fetch without a hash Stephen Paul Weber
2022-12-21 22:49 ` Ludovic Courtès
2023-01-03 19:31 ` Stephen Paul Weber [this message]
2023-01-03 21:34 ` Ludovic Courtès
2023-01-05 10:06 ` Simon Tournier
2023-01-09 11:16 ` Ludovic Courtès
2023-01-11 15:34 ` Simon Tournier
2023-02-05 17:44 ` bokr
2023-02-06 17:01 ` Simon Tournier
2023-01-09 17:13 ` Ludovic Courtès
2023-01-09 17:35 ` Stephen Paul Weber
2023-01-17 16:01 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y7SCiE9URY5K//zX@singpolyma-beefy.lan \
--to=singpolyma@singpolyma.net \
--cc=0@psycoti.ca \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.