From: ludo@gnu.org (Ludovic Courtès)
To: Jeff Mickey <j@codemac.net>
Cc: guix-devel@gnu.org
Subject: Re: The problem of "guix build emacs --with-source=./emacs"
Date: Fri, 13 Nov 2015 09:44:01 +0100 [thread overview]
Message-ID: <87si4ap9v2.fsf@gnu.org> (raw)
In-Reply-To: <87k2pmvqpk.fsf@codemac.net> (Jeff Mickey's message of "Thu, 12 Nov 2015 13:43:35 -0800")
Jeff Mickey <j@codemac.net> skribis:
> Forgot to CC the list...
>
> * Ludovic Courtès <ludo@gnu.org> [2015-11-12 04:49]:
>> tumashu <tumashu@163.com> skribis:
>>
>>> When I use the below command to build emacs from emacs.git
>>>
>>> guix build emacs --with-source=./emacs (emacs dir is git repo)
>>>
>>> Build fail, after i remove the .git, build success.
>>
>> Could you explain how it fails exactly, and post the tail of the
>> build log?
>>
>>> The repo of emacs.git is 1.5G, is it the reason?
>>
>> I don’t think so. That certainly makes it a bad option, though.
>>
>> Thanks,
>> Ludo’.
>
> Isn't the emacs/.git dir is included in the hash calculation if it's
> left in there?
Yes.
> I believe that guix calculates these hashes without the .git dir
> IIRC. Not sure of great ways to work around this without moving the
> './emacs/.git' dir outside of ./emacs during your build, as .git dirs
> contain all kinds of non-reproducible state on disk
Correct. So keeping the .git directory indeed makes the thing
“unreproducible” in the sense that nobody else will get the same .git
directory. But it may be acceptable if all you want is to make a
one-off build.
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-11-13 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 1:51 The problem of "guix build emacs --with-source=./emacs" tumashu
2015-11-12 12:49 ` Ludovic Courtès
[not found] ` <87pozf2fcf.fsf@codemac.net>
2015-11-12 21:43 ` Jeff Mickey
2015-11-13 8:44 ` Ludovic Courtès [this message]
2015-11-13 0:31 ` tumashu
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=87si4ap9v2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=j@codemac.net \
/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.