Subject: Re: bug#37047: git needs sed either as propagated input or as input (with some substitute*-work)

From: Ludovic Courtès <[email-masked]>
Date: Wed, 28 Aug 2019 22:39:03 +0200

Hi Björn,

Björn Höfling <[email-masked]> skribis:

> guix environment --container -N --ad-hoc go coreutils binutils less  emacs grep findutils git nss-certs
>
> [env] $ go get github.com/fatih/structs 
> # cd /home/bjoern/go/src/github.com/fatih/structs; git submodule update --init --recursive
> /gnu/store/i89f4rw8a2nzppxf2yixl0hvcw46rsxv-git-2.22.0/libexec/git-core/.git-submodule-real: line 7: sed: command not found
> /gnu/store/kiykcyp4n45c7prba3k3zvfz19vvmymd-profile/libexec/git-core/git-sh-setup: line 86: sed: command not found
> /gnu/store/i89f4rw8a2nzppxf2yixl0hvcw46rsxv-git-2.22.0/libexec/git-core/.git-submodule-real: line 1115: sed: command not found
> /gnu/store/i89f4rw8a2nzppxf2yixl0hvcw46rsxv-git-2.22.0/libexec/git-core/.git-submodule-real: line 1115: cmd_: command not found
> package github.com/fatih/structs: exit status 127

I vote for ‘substitute*’ trickery in libexec/git-core/*.

Ludo’.