unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "(" <paren@disroot.org>, Julien Lepiller <julien@lepiller.eu>,
	56030@debbugs.gnu.org
Subject: bug#56030: The guix pull profile is too big
Date: Thu, 21 Jul 2022 17:46:38 +0200	[thread overview]
Message-ID: <22b12576-51f2-2396-a52c-b6956ecd88b5@telenet.be> (raw)
In-Reply-To: <CLLFIQ1OG10K.BVBWA00UIAGE@guix-aspire>


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


On 21-07-2022 17:11, ( wrote:
> couldn't we just use `-DSHELL_PATH=/gnu/store/...`?

Using SHELL_PATH instead of the __guix_bin_sh sounds better, yes.  But 
it's not 'just use -DSHELL_PATH=', we still need to change 'system' 
appropriately.

> Would this not violate POSIX? Since, as far as I can see,
> <https://pubs.opengroup.org/onlinepubs/9699919799/functions/system.html>
> does not give the implementation license to implement system(3) as a
> macro.
Probably. But does that really matter?  The standard exists for a 
reason, but we aren't aiming for POSIX certifications and it isn't the 
law or something ... seems rather inconvenient for development outside a 
build environment though, so perhaps SHELL_PATH could somehow fallback 
to /bin/sh when outside a build environment.
>   We could do
>
> ```
> int system(const char *command) {
> 	return __guix_run_in_shell(command, __guix_bin_sh);
> }

Needs a 'static' to avoid multiple definitions on the same thing, but 
yes, that would avoid the macro problem (though not sufficient for some 
FFI).

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 --]

  parent reply	other threads:[~2022-07-21 15:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  5:48 bug#56030: The guix pull profile is too big Julien Lepiller
2022-06-26 21:20 ` Ludovic Courtès
2022-08-30 10:04   ` zimoun
2022-07-21 14:52 ` Maxime Devos
2022-07-21 15:03   ` paren--- via Bug reports for GNU Guix
2022-07-21 15:38     ` paren--- via Bug reports for GNU Guix
2022-08-06 23:37     ` bug#56030: rfc2822 permits that left paren, but why do it? -- was " bokr
2022-07-21 15:11   ` paren--- via Bug reports for GNU Guix
2022-07-21 15:42     ` Julien Lepiller
2022-07-21 15:48       ` paren--- via Bug reports for GNU Guix
2022-07-21 15:52         ` paren--- via Bug reports for GNU Guix
2022-07-21 15:46     ` Maxime Devos [this message]
2022-07-21 15:49       ` paren--- via Bug reports for GNU Guix
2022-07-21 15:52         ` Julien Lepiller
2022-07-21 15:53         ` Maxime Devos
2022-07-21 16:13   ` paren--- via Bug reports for GNU Guix
2022-07-21 16:22     ` Maxime Devos
2022-07-21 16:29       ` paren--- via Bug reports for GNU Guix
2022-07-21 16:35         ` Maxime Devos

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=22b12576-51f2-2396-a52c-b6956ecd88b5@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56030@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=paren@disroot.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).