unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-patches@gnu.org
Cc: 66537@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Hiep Pham" <hiepph9@proton.me>
Subject: bug#66537: [PATCH] doc: Recommend building in ‘guix shell -CPW’.
Date: Wed, 29 Nov 2023 20:33:55 +0100	[thread overview]
Message-ID: <87fs0o5p7g.fsf@gmail.com> (raw)
In-Reply-To: <2d49ea4ddadceb4a3017f1a6032fb2858616cdee.1700654648.git.ludo@gnu.org>

Hi,

On mer., 22 nov. 2023 at 13:05, Ludovic Courtès <ludo@gnu.org> wrote:

>  @example
> -guix shell -D guix --pure
> +guix shell -D guix -CPW
>  @end example
>  
>  or even, from within a Git worktree for Guix:
>  
>  @example
> -guix shell --pure
> +guix shell -CPW
>  @end example

I would not recommend that or adding also the option -N.  Else, the
development experience can be annoying.

For instance, “make check” will probably fail because some substitutes
are missing (see #67532 [1], e.g., tests/derivations.scm).

Moreover, one needs to go out the shell for submitting with “git
send-email” but then git:send-email is not necessary available in PATH.

1: https://issues.guix.gnu.org/issue/67532


Cheers,
simon




  reply	other threads:[~2023-11-30  9:58 UTC|newest]

Thread overview: 7+ 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 [this message]
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

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=87fs0o5p7g.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=66537@debbugs.gnu.org \
    --cc=guix-patches@gnu.org \
    --cc=hiepph9@proton.me \
    --cc=ludo@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).