From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: guix: git: Add new module.
Date: Sat, 06 May 2017 14:39:26 +0200 [thread overview]
Message-ID: <87efw2w45d.fsf@gnu.org> (raw)
In-Reply-To: <8737ciwfvy.fsf@gmail.com> (Mathieu Othacehe's message of "Sat, 06 May 2017 10:25:53 +0200")
Hi,
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
> Thanks for taking care of it.
>
>> I could not reproduce the failure when building "by hand", but since
>> `guix pull` is the primary method of updating Guix, I reverted this
>> change for now:
>
> I guess it is because in (guix build pull) every single file is
> builded, without take configure/makefile consigns into account.
Yes, see build-aux/build-self.scm.
> Except a horrible hack (an exception list in "build-guix"), I don't see
> how to deal with it. Maybe this commit shall be put on a branch or wait
> until guix switches to guile2.2.
>
> Ludo any thoughs ?
I plan to update ‘guix pull’ for Guile 2.2 before the release:
https://lists.gnu.org/archive/html/guix-devel/2017-04/msg00515.html
When it’s done, we could add Guile-Git as an input when 2.2 is used, and
maybe add a special case for (guix git).
Thoughts?
Ludo’.
next prev parent reply other threads:[~2017-05-06 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170505175324.13769.79863@vcs0.savannah.gnu.org>
[not found] ` <20170505175325.5D41920E7B@vcs0.savannah.gnu.org>
2017-05-06 0:15 ` 01/01: guix: git: Add new module Leo Famulari
2017-05-06 8:25 ` Mathieu Othacehe
2017-05-06 12:39 ` Ludovic Courtès [this message]
2017-05-06 12:55 ` Mathieu Othacehe
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=87efw2w45d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=m.othacehe@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).