all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 67366-done@debbugs.gnu.org
Cc: 66537-done@debbugs.gnu.org, Hiep Pham <hiepph9@proton.me>
Subject: bug#67366: [PATCH] doc: Recommend building in ‘guix shell -CPW’.
Date: Mon, 04 Dec 2023 22:51:51 +0100	[thread overview]
Message-ID: <87sf4hljpk.fsf@gnu.org> (raw)
In-Reply-To: <2d49ea4ddadceb4a3017f1a6032fb2858616cdee.1700654648.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Wed, 22 Nov 2023 13:05:30 +0100")

Ludovic Courtès <ludo@gnu.org> skribis:

> This was prompted by <https://issues.guix.gnu.org/66537>, where someone
> tried to build Guix within ‘guix shell --pure’ on a foreign distro and
> found that ./configure would pick software from the host system.
>
> Suggested by Hiep Pham <hiepph9@proton.me>.
>
> * doc/contributing.texi (Building from Git): Recommend ‘guix shell -CPW’.
>
> Change-Id: I7694b482d982917fef6ec404f68ddacea761f482

Pushed as 01361d46b8e0481ad56665d7a06c276b08f59c6d.

Ludo'.




      parent reply	other threads:[~2023-12-04 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-14 12:49 bug#66537: configure: error: The Guile bindings of GnuTLS are missing Hiep Pham via Bug reports for GNU Guix
2023-10-17  8:59 ` Daniel Meißner via Bug reports for GNU Guix
2023-10-17 10:28   ` Hiep Pham via Bug reports for GNU Guix
2023-11-22 12:05     ` bug#66537: [PATCH] doc: Recommend building in ‘guix shell -CPW’ Ludovic Courtès
2023-11-29 19:33       ` Simon Tournier
2023-12-08 15:50         ` bug#66537: configure: error: The Guile bindings of GnuTLS are missing Simon Tournier
2023-12-19  9:30           ` bug#66537: [PATCH] doc: Recommend building in ‘guix shell -CPW’ Simon Tournier
2023-12-04 21:51       ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sf4hljpk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=66537-done@debbugs.gnu.org \
    --cc=67366-done@debbugs.gnu.org \
    --cc=hiepph9@proton.me \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.