GNU bug report logs -
#36592
no output for guix package -f when the file evaluates to nothing
Previous Next
Reported by: Julien Lepiller <julien <at> lepiller.eu>
Date: Thu, 11 Jul 2019 09:32:02 UTC
Severity: normal
Tags: easy
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Fri, 20 Sep 2019 09:42:22 +0200
with message-id <87mueztnvl.fsf <at> gnu.org>
and subject line Re: bug#36592: no output for guix package -f when the file evaluates to nothing
has caused the debbugs.gnu.org bug report #36592,
regarding no output for guix package -f when the file evaluates to nothing
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
36592: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36592
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Users tend to copy what they see in our code base, so it's not rare to have to help them realise that if their last statement is (define-public ...), the file doesn't evaluate to a package.
Running guix build -f mypackage.scm at least gives an error saying it doesn't know how to compile #<unspecified>.
Running guix package -f mypackage.scm returns immediately with no error message and a status of 0, but doesn't actually build or install anything. You can even try with an empty file :)
There should be an error message, and probably even a hint.
[Message part 3 (message/rfc822, inline)]
Hello,
Julien Lepiller <julien <at> lepiller.eu> skribis:
> Users tend to copy what they see in our code base, so it's not rare to have to help them realise that if their last statement is (define-public ...), the file doesn't evaluate to a package.
>
> Running guix build -f mypackage.scm at least gives an error saying it doesn't know how to compile #<unspecified>.
>
> Running guix package -f mypackage.scm returns immediately with no error message and a status of 0, but doesn't actually build or install anything. You can even try with an empty file :)
>
> There should be an error message, and probably even a hint.
Fixed in f9c0400392843540a87985a67ffb9fb6e4dbc2fa. It doesn’t provide a
hint though.
I thought we may want to provide ‘load*’ a type predicate that it would
check, so that it can say “got #<undefined>, expected <package>”.
However, we’d need a contract rather than a mere predicate to have nice
error reporting, so I decided to punt on this for now.
Ludo’.
This bug report was last modified 5 years and 283 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.