From: Ricardo Wurmus <rekado@elephly.net>
To: divoplade <d@divoplade.fr>
Cc: help-guix@gnu.org
Subject: Re: The sources with a git ref origin should also include the .git directory
Date: Sat, 01 Aug 2020 15:25:29 +0200 [thread overview]
Message-ID: <87bljuh512.fsf@elephly.net> (raw)
In-Reply-To: <1eef66018703ced70a6e4b81e1297519e234645e.camel@divoplade.fr>
divoplade <d@divoplade.fr> writes:
> I am in the process of writing some code, and I like the fact that the
> source of a guix package can have a git reference. However, when I use
> it, the .git directory is not present when building the source.
That’s on purpose, because the .git directory contains files that
prevent reproducibility.
--
Ricardo
next prev parent reply other threads:[~2020-08-01 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 12:50 The sources with a git ref origin should also include the .git directory divoplade
2020-08-01 13:25 ` Ricardo Wurmus [this message]
2020-08-01 13:41 ` 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=87bljuh512.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=d@divoplade.fr \
--cc=help-guix@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.
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).