From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org
Subject: Packages depending on (guix build syscalls)
Date: Thu, 20 Oct 2022 22:05:50 +0200 [thread overview]
Message-ID: <87v8oeb6qp.fsf@inria.fr> (raw)
Hello Guix!
Quite a few packages depend on (guix build syscalls), starting from
‘ant-bootstrap’ (since commit cded3a759356ff66b7df668bcdbdfa0daf96f4c5
in 2018) up to GNOME-related packages such as ‘mutter’ (commit
d1c2fe248a7a326189fb7dcae64a59ece96251ba a few months ago).
It’s great that we can reuse this module in different contexts! The
downside is that the module evolves quite often, because it’s a
foundation for Guix System and other things. As a result, all these
packages get rebuilt every time we change it.
Maybe the only recommendation I would have is that we should make sure
we really need it before having a package deep down the graph depend on
it. I wouldn’t want us to do ‘staging’ cycles when we need a change in
(guix build syscalls).
Thoughts?
Ludo’.
next reply other threads:[~2022-10-20 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 20:05 Ludovic Courtès [this message]
2022-10-21 5:57 ` Packages depending on (guix build syscalls) Maxime Devos
2022-10-21 8:18 ` Ludovic Courtès
2022-10-21 8:16 ` 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://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=87v8oeb6qp.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=guile-devel@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).