Re: Packages depending on (guix build syscalls)

[Maxime Devos <maximedevos@telenet.be>]

[-- Attachment #1.1.1: Type: text/plain, Size: 1229 bytes --]

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 #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]