From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 36371@debbugs.gnu.org
Subject: bug#36371: guix build --with-git-reference=…
Date: Tue, 25 Jun 2019 14:38:44 +0200 [thread overview]
Message-ID: <871rzhon57.fsf@gnu.org> (raw)
In-Reply-To: <87mui6rp9q.fsf@nckx> (Tobias Geerinckx-Rice's message of "Tue, 25 Jun 2019 11:24:33 +0200")
Hi!
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> bricewge on #guix informed me that there's no way to pass a git tag as
> source transformation option. Indeed:
>
> ‘--with-commit=PACKAGE=COMMIT’
> This is similar to ‘--with-branch’, except that it builds from
> COMMIT rather than the tip of a branch. COMMIT must be a valid
> Git
> commit SHA1 identifier.
Indeed:
--8<---------------cut here---------------start------------->8---
$ guix build guile-gcrypt --with-commit=guile-gcrypt=v1.0.0
updating checkout of 'https://notabug.org/cwebber/guile-gcrypt.git'...
guix build: error: cannot fetch commit v1.0.0 from https://notabug.org/cwebber/guile-gcrypt.git: unable to parse OID - contains invalid characters
--8<---------------cut here---------------end--------------->8---
Internally, that uses the ‘git-checkout’ record type defined in (guix
git).
What I would propose is to change ‘git-checkout-compiler’ so that it can
determine with a simple heuristic like that of (@@ (guix swh) commit-id?)
whether the string denotes a commit ID or a tag.
WDYT?
> - Why is the (extremely) git-specific ‘--with-commit=’ option not
> called ‘--with-git-commit=’? Was it intended to be more generic than
> it is now? Should the new option be ‘--with-reference=’ as well?
> That's pushing it a little far. And three questions in one; I'm
> cheating.
Things are named this way for simplicity; the only exception is
‘--with-git-url’ because ‘--with-url’ would have been too vague.
Ludo’.
next prev parent reply other threads:[~2019-06-25 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 9:24 bug#36371: guix build --with-git-reference=… Tobias Geerinckx-Rice
2019-06-25 12:38 ` Ludovic Courtès [this message]
2019-07-26 10:38 ` 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
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=871rzhon57.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36371@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).