unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <marius@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Packages depending on (guix build syscalls)
Date: Wed, 02 Nov 2022 11:22:23 +0100	[thread overview]
Message-ID: <87r0ylwt9c.fsf@gnu.org> (raw)
In-Reply-To: <87bkq2tssw.fsf@gnu.org> (Marius Bakke's message of "Sun, 23 Oct 2022 18:21:03 +0200")

Hi!

Marius Bakke <marius@gnu.org> skribis:

> Ludovic Courtès <ludo@gnu.org> skriver:
>
>> Ludovic Courtès <ludo@gnu.org> skribis:
>>
>>> 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 seems the usage of (guix build syscalls) in java.scm and
> ant-build-system is solely for 'mkdtemp!'.  Guile 3.0.6 gained
> 'mkdtemp', so I suppose we can switch to that?

I think so.

> If there are backwards-compatibility concerns it seems possible to
> modify these procedures to not need to 'mkdtemp' at all.
>
> I can prepare a patch along these lines, but not sure if we need to
> maintain backward compatibility in (gnu packages).

In (gnu packages)?

The only thing to keep in mind is that (guix build gnu-build-system) is
used by packages in commencement.scm, which run on Guile 2.0; thus
gnu-build-system.scm cannot rely on features that appeared in Guile 3.0.
However, for ant-build-system.scm it’s fine to rely on those.

Thanks,
Ludo’.


  reply	other threads:[~2022-11-02 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  8:15 Packages depending on (guix build syscalls) Ludovic Courtès
2022-10-21  9:03 ` Ludovic Courtès
2022-10-22 19:14   ` Efraim Flashner
2022-10-27  3:31     ` Maxim Cournoyer
2022-10-27  8:27       ` Efraim Flashner
2022-10-23 16:21   ` Marius Bakke
2022-11-02 10:22     ` Ludovic Courtès [this message]
2022-11-11 17:31       ` Marius Bakke
2022-10-22 14:08 ` Maxim Cournoyer
2022-10-22 14:12 ` Maxim Cournoyer

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=87r0ylwt9c.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=marius@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.
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).