From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, guix-devel@gnu.org
Subject: Re: New review checklist
Date: Fri, 01 Apr 2022 08:30:07 +0200 [thread overview]
Message-ID: <b1cc68f064c3c2ebfc43669be052a4ae926dedb0.camel@telenet.be> (raw)
In-Reply-To: <0912e3091c2bc34866f2795ec4f0413fc0928bdc.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
Liliana Marie Prikler schreef op vr 01-04-2022 om 06:14 [+0200]:
> It won't be added to Guix. Here's why it won't.
> You appear to believe that
> [...]
> [ ] hard-coding the commit field is a good idea
Does the following count:
(define-public foo
(package
(name "foo")
(version "1.0.0")
(source
(origin
[...]
(file-name (git-file-name name version))
;; Upstream does not tag versions, see
;; <https://foo.bar/versions> for which commit
;; corresponds to which version.
;;
;; (alternatively)
;;
;; Upstream deletes old tags every N months,
;; so explicitly write the commit here.;
;;
;; (alternatively)
;;
;; There is consensus that the benefits of explicit commits
;; outweigh the downsides, see
;; <https://actually.I.dont.think.there.is.consensus?>
(commit "cabba9e..."))
[...]))
-- would the commit need to be let-bound here?
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-01 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 4:14 New review checklist Liliana Marie Prikler
2022-04-01 6:30 ` Maxime Devos [this message]
2022-04-01 17:03 ` Liliana Marie Prikler
2022-04-01 17:46 ` Maxime Devos
2022-04-01 18:25 ` Liliana Marie Prikler
2022-04-02 13:38 ` Bengt Richter
2022-04-02 14:45 ` Liliana Marie Prikler
2022-04-01 18:05 ` Tobias Geerinckx-Rice
2022-04-01 6:56 ` tanguy
2022-04-01 8:31 ` Jonathan McHugh
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=b1cc68f064c3c2ebfc43669be052a4ae926dedb0.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).