From: divoplade <d@divoplade.fr>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>,
John Cowan <cowan@ccil.org>
Cc: guile-user@gnu.org
Subject: Re: Help making a GNU Guix package for pure GNU Guile library
Date: Sat, 30 Jan 2021 21:16:16 +0100 [thread overview]
Message-ID: <bb8fb0c5bacb14c44102fc7e193d7a2ecdfdfe38.camel@divoplade.fr> (raw)
In-Reply-To: <87v9be5hyc.fsf@web.de>
Hello,
Le samedi 30 janvier 2021 à 20:43 +0100, Dr. Arne Babenhauserheide a
écrit :
> I think configure-runs should be slimmed down by a first check
> whether
> it’s in a known environment (so 90% of the tests can be skipped). But
> that’s not a general complaint about the approach of autotools.
The configure script can use a cache file (
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.70/html_node/Cache-Files.html
), so this can discard some of the tests and speed up things. Since we
are talking about guix (the perfect example of a "known environment",
in my opinion), maybe it could be a feature of guix to generate this
file automatically.
next prev parent reply other threads:[~2021-01-30 20:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 17:17 Help making a GNU Guix package for pure GNU Guile library Zelphir Kaltstahl
2021-01-30 17:55 ` Jérémy Korwin-Zmijowski
2021-01-30 19:56 ` divoplade
2021-01-31 3:26 ` Zelphir Kaltstahl
2021-01-30 18:35 ` John Cowan
2021-01-30 19:43 ` Dr. Arne Babenhauserheide
2021-01-30 20:16 ` divoplade [this message]
2021-01-30 21:15 ` Ricardo Wurmus
2021-01-31 0:26 ` build system for pure Guile library (was Re: Help making a GNU Guix package for pure GNU Guile library) pelzflorian (Florian Pelz)
2021-01-31 6:29 ` Ricardo Wurmus
2021-01-31 14:16 ` Zelphir Kaltstahl
2021-01-31 15:38 ` Dr. Arne Babenhauserheide
2021-02-03 23:07 ` Zelphir Kaltstahl
2021-02-04 0:09 ` Ricardo Wurmus
2021-02-03 18:31 ` Adriano Peluso
2021-01-31 3:19 ` Help making a GNU Guix package for pure GNU Guile library Zelphir Kaltstahl
2021-02-03 18:43 ` Adriano Peluso
2021-02-03 23:12 ` Zelphir Kaltstahl
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb8fb0c5bacb14c44102fc7e193d7a2ecdfdfe38.camel@divoplade.fr \
--to=d@divoplade.fr \
--cc=arne_bab@web.de \
--cc=cowan@ccil.org \
--cc=guile-user@gnu.org \
/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.
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).