Vincent Legoll skribis:
>>> Or maybe I'm very bad at info, always found its interface weird...
>>
>> I'm not sure, I actually don't use `info` very much either. Maybe your
>> GuixSD installation has not been updated since the relevant text was
>> added to the manual?
>
> I regularly do guix pull
Hi,
David Craven skribis:
> When adding cross-compilation support to the linux-libre package I
> noticed that native-inputs are in #:key native-inputs when
> cross-compiling but not when compiling natively. I think this is a
> problem because we can't just use #:key native-inputs instead of #:ke
> It’s on purpose, and packages rarely (if even) need to refer to
> #:native-inputs; only a couple of phases in gnu-build-system.scm refer
> to #:native-inputs.
>
> In which context do you need to refer to #:native-inputs?
Cross-compiling the linux kernel.
> ;; Apply the neat patch.
> (system* "p
Quoting Ludovic Courtès (2016-09-01 04:59:02)
> ‘exec -a’ works as advertised:
>
> --8<---cut here---start->8---
> $ sh -c 'exec -a FOO guile -c "(pk (command-line))"'
>
> ;;; (("FOO"))
> --8<---cut here---end--->8---
So, he
David Craven skribis:
>> It’s on purpose, and packages rarely (if even) need to refer to
>> #:native-inputs; only a couple of phases in gnu-build-system.scm refer
>> to #:native-inputs.
>>
>> In which context do you need to refer to #:native-inputs?
>
> Cross-compiling the linux kernel.
>
>> ;; A
> (assoc-ref (or native-inputs inputs) "bash")
Yes, that's not too bad. Thanks!
I'll wait for someone to comment the patches I've already submitted to
the mailing list (to see if they are cosher :) before making the
changes.
FYI: I rebuilt linux-libre-headers but the tar test-suite kept
crashin
I suspect the scope of this UX "bug" is larger than python. I think this
probably affects every executable written in an interpreted
language and using a shebang. Here's another example with a bash
script:
$ cat > t.sh
#!/bin/bash
sed 's/\x0/\\0/g' # replaces null bytes with a visible '\
Hello,
l...@gnu.org (Ludovic Courtès) skribis:
> $ sh -c 'exec -a FOO
> /gnu/store/6vmniz83k46l8jpry50wdvwxsncz1r5w-khal-0.7.0/bin/.khal-wrap-01
> --version'
> .khal-real, version 0.7.0
What happens is that ‘exec -a’ is doesn’t work when the wrapped program
is a script.
This is because, when
