guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Packages depending on (guix build syscalls)


From: Maxime Devos
Subject: Re: Packages depending on (guix build syscalls)
Date: Fri, 21 Oct 2022 07:57:00 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1

On 20-10-2022 22:05, Ludovic Courtès wrote:
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). [...]
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?

antioxidant.scm (used by all Rust packages in antioxidant-build-system) uses 'scandir*' from (guix build syscalls), though that one looks like simply be replaced by 'scandir'.

The same holds for antioxidant-workspaces.scm (used by a few Rust packages, but not, say librsvg).

They will have to be adjusted, then.

Additionally, to me it looks like a few of the things in (guix build syscalls) could be eventually moved in Guile itself, e.g. mktemp!, fdatasync and setxattr, which could eventually reduce the need of packages to import (guix build syscalls).

Greetings,
Maxime.

Attachment: OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]