> See ‘package-from-tarball’ for an example, in bootstrap.scm.
Thanks. Can I push the attached patch along with this one [1,2]?
Two questions, though:
1. Is it necessary to use 'begin' here?
(begin
(mkdir out)
(copy-file tarball "grue-hunter.tar.gz")
...)
2. I'd like to use
(patch-sheb
> That could be done by changing ‘gnupg-verify*’. An optional argument
> could be added to select between interactive behavior (“do you want to
> download this key and add it to your keyring?”), always-download, and
> never-download.
I'm attaching my attempt.
There are two similar but unrelated
l...@gnu.org (Ludovic Courtès) skribis:
> Cojocaru Alexandru skribis:
>
>> the build process fails, this is the message I get:
>> ;;; Failed to autoload find-newest-available-packages in (gnu packages):
>> ;;; ERROR: Syntax error:
>> ;;; gnu/packages.scm:94:22: source expression failed to match a
Cyril Roelandt skribis:
> On 05/23/2013 02:19 PM, Ludovic Courtès wrote:
>> Cyril Roelandt skribis:
>>
>>> * gnu/packages/babel.scm: New file.
>>> * Makefile.am (MODULES): Add it.
>>
>> OK!
>>
>
>
> Well, maybe this should go to python.scm, just like pytz. What do you
> think ?
Yes, makes sense
Andreas Enge skribis:
> Download of substituted binaries fails when one is offline. This is
> logical, but should guix then not gracefully fall back to compilation if
> the sources have already been downloaded?
I just added the ‘--fallback’ option for “guix build” and “guix package”.
So by def
Download of substituted binaries fails when one is offline. This is
logical, but should guix then not gracefully fall back to compilation if
the sources have already been downloaded?
In any case, catching the error and emitting an error message would
probably be preferable to
$ guix build hell
