From: Julien Lepiller <julien@lepiller.eu>
To: "(" <paren@disroot.org>, Maxime Devos <maximedevos@telenet.be>,
56030@debbugs.gnu.org
Subject: bug#56030: The guix pull profile is too big
Date: Thu, 21 Jul 2022 17:52:25 +0200 [thread overview]
Message-ID: <3D5439F2-F6AE-4F19-9254-16E5BD7440DC@lepiller.eu> (raw)
In-Reply-To: <CLLGBK9M3110.2MID4Q9LBQ70N@guix-aspire>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
I must have misunderstood, I thought you wanted to pass it during the build of glibc.
Le 21 juillet 2022 17:49:36 GMT+02:00, "(" <paren@disroot.org> a écrit :
>On Thu Jul 21, 2022 at 4:46 PM BST, Maxime Devos wrote:
>> 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.
>Why would we need to change it? The glibc definition already uses that
>macro for the shell path, it's just hard-coded to /bin/sh by default.
[-- Attachment #2: Type: text/html, Size: 931 bytes --]
next prev parent reply other threads:[~2022-07-21 15:54 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
2022-07-21 15:49 ` paren--- via Bug reports for GNU Guix
2022-07-21 15:52 ` Julien Lepiller [this message]
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=3D5439F2-F6AE-4F19-9254-16E5BD7440DC@lepiller.eu \
--to=julien@lepiller.eu \
--cc=56030@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--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).