From: Robert Vollmert <rob@vllmrt.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Guix beyond 1.0: let’s have a roadmap!
Date: Tue, 9 Jul 2019 12:58:58 +0200 [thread overview]
Message-ID: <93F86808-622C-48B9-AC6E-10432193FB1F@vllmrt.net> (raw)
In-Reply-To: <87d0ijjymp.fsf@elephly.net>
> On 9. Jul 2019, at 12:22, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Hi Robert,
>
>>>> - more consistent and useful output — currently it’s very easy to miss the
>>>> actual cause of an error between a lot of noise, e.g. all those “recompiling
>>>> scheme module” messages
>>>
>>> When do you see “recompiling” messages?
>>
>> Here’s an example: ~/guix-postgrest$ guix build -L . postgrest
>> ;;; note: source file ./bytestring.scm
>> ;;; newer than compiled /gnu/store/r6w8vjfdii0pscbp6lmy6siqvzy2lgcn-postgrest/lib/guile/2.2/site-ccache/bytestring.go
>> ;;; note: source file ./check.scm
>> ;;; newer than compiled /gnu/store/r6w8vjfdii0pscbp6lmy6siqvzy2lgcn-postgrest/lib/guile/2.2/site-ccache/check.go
>
> This is certainly not normal. Why do you use “-L .” here?
~/guix-postgrest is a git repository that houses some in-development packages of mine.
E.g. there’s a file postgrest.scm that has the definition of the postgrest package,
and the file check.scm that has definitions of a number haskell dependencies that
are not in guix proper yet.
guix build -L . <package-name>
then seems like the straightforward way to interactively test that package definition
without going through any git push, guix pull etc.
> Having the messages is good, though, because interpreting these files
> instead of using the compiled variants comes with a massive drop in
> performance.
Why doesn’t guile silently do the right thing instead?
Cheers
Robert
next prev parent reply other threads:[~2019-07-09 10:59 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 16:05 Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 16:36 ` P
2019-06-27 21:12 ` Ludovic Courtès
2019-06-27 17:06 ` Vagrant Cascadian
2019-06-27 21:17 ` Ludovic Courtès
2019-06-27 18:53 ` Jakob L. Kreuze
2019-06-27 21:18 ` Ludovic Courtès
2019-06-27 19:02 ` Alex Griffin
2019-06-27 22:33 ` swedebugia
2019-06-28 6:11 ` Julien Lepiller
2019-06-28 16:13 ` John Soo
2019-07-01 9:14 ` Ludovic Courtès
2019-07-01 11:57 ` Pierre Neidhardt
2019-07-07 14:15 ` Ludovic Courtès
2019-06-30 13:48 ` Giovanni Biscuolo
2019-07-01 9:16 ` Ludovic Courtès
2019-07-05 7:55 ` Giovanni Biscuolo
2019-07-01 10:05 ` Ludovic Courtès
2019-07-01 13:12 ` Alex Griffin
2019-07-05 8:35 ` Guix UCI comparison (was Re: Guix beyond 1.0: let’s have a roadmap!) Giovanni Biscuolo
2019-07-07 14:09 ` Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 19:33 ` Svante Signell
2019-06-27 21:25 ` Ludovic Courtès
2019-06-27 20:28 ` Thompson, David
2019-07-01 9:36 ` Ludovic Courtès
2019-07-01 10:39 ` Hartmut Goebel
2019-07-01 9:37 ` Ludovic Courtès
2019-06-27 22:01 ` Pierre Neidhardt
2019-06-27 22:24 ` Julien Lepiller
2019-07-01 9:48 ` Ludovic Courtès
2019-06-28 16:54 ` znavko
2019-06-28 17:07 ` swedebugia
2019-06-28 17:17 ` znavko
2019-06-29 1:35 ` ison
2019-06-29 4:51 ` pelzflorian (Florian Pelz)
2019-07-01 9:51 ` Ludovic Courtès
2019-06-30 13:13 ` Giovanni Biscuolo
2019-06-30 13:38 ` Robert Vollmert
2019-07-01 9:55 ` Ludovic Courtès
2019-07-05 11:47 ` Robert Vollmert
2019-07-09 10:22 ` Ricardo Wurmus
2019-07-09 10:58 ` Robert Vollmert [this message]
[not found] ` <877e97vws8.fsf%40gnu.org504D1A97-2EBD-46A1-85B8-091C923DD6A1@vllmrt.net>
2019-07-26 7:00 ` Ben Sturmfels
2019-07-26 8:27 ` Pierre Neidhardt
2019-08-22 20:59 ` Ludovic Courtès
2019-06-30 13:28 ` Christopher Lemmer Webber
2019-07-01 9:57 ` Ludovic Courtès
2019-07-01 11:47 ` Pierre Neidhardt
2019-06-30 13:59 ` Giovanni Biscuolo
2019-07-01 9:58 ` Ludovic Courtès
2019-07-09 13:32 ` P
2019-07-11 10:11 ` Ricardo Wurmus
2019-07-11 15:17 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2019-06-28 18:57 Jesse Gibbons
2019-07-01 10:14 ` zimoun
2019-07-01 19:38 ` Jesse Gibbons
2019-07-06 12:50 matias_jose_seco
2019-07-07 14:20 ` Ludovic Courtès
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=93F86808-622C-48B9-AC6E-10432193FB1F@vllmrt.net \
--to=rob@vllmrt.net \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).