unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: paren--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Maxime Devos" <maximedevos@telenet.be>,
	"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:13:54 +0100	[thread overview]
Message-ID: <CLLGU659UBKV.2M04RRSCIHKYE@guix-aspire> (raw)
In-Reply-To: <d644f79a-f0e3-6166-23cc-db867577f048@telenet.be>

Okay, another (hopefully more coherent) proposal: Patch in a

```
extern char *__guix_shell_path;
```

And then, we use a linker script to provide the definition of
__guix_shell_path at linking time. (Unfortunately there's no way to do
this with a flag, afaik...)

    -- (




  parent reply	other threads:[~2022-07-21 16:18 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
2022-07-21 15:53         ` Maxime Devos
2022-07-21 16:13   ` paren--- via Bug reports for GNU Guix [this message]
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=CLLGU659UBKV.2M04RRSCIHKYE@guix-aspire \
    --to=bug-guix@gnu.org \
    --cc=56030@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --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).