unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38455@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: [bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage.
Date: Tue, 3 Dec 2019 11:34:42 +0100	[thread overview]
Message-ID: <CAJ3okZ2m7oi-Pgz=xx+F5viLBV99-sVjBkx4g60zqYCTiFzvug@mail.gmail.com> (raw)
In-Reply-To: <20191202203157.70c0310c@scratchpost.org>

Hi Danny,

On Mon, 2 Dec 2019 at 20:33, Danny Milosavljevic <dannym@scratchpost.org> wrote:


> good idea, but I use
>
> $ guix environment --pure guix --ad-hoc git guile-readline guile-json

I think that it is described here [1]

[1] https://guix.gnu.org/manual/en/guix.html#Building-from-Git


From my point of view, the change should only concern how to test
"guix pull" by adding a bullet -- with a link to Building from Git and
 Running Test Suite.


> (Not using "--pure" is asking for trouble in my opinion)

I agree that --pure should be always added to avoid troubles.
Maybe it should be the default of "guix environment"?


Cheers,
simon

  parent reply	other threads:[~2019-12-03 10:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02  9:15 [bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage Pierre Neidhardt
2019-12-02 12:08 ` zimoun
2019-12-02 12:16   ` Pierre Neidhardt
2019-12-02 12:32     ` zimoun
2019-12-02 12:48       ` zimoun
2019-12-02 19:31 ` Danny Milosavljevic
2019-12-02 20:14   ` Pierre Neidhardt
2019-12-02 21:48     ` Danny Milosavljevic
2019-12-03 10:39       ` zimoun
2019-12-03 10:34   ` zimoun [this message]
2019-12-08 15:42     ` Pierre Neidhardt
2019-12-12 15:55       ` zimoun
2019-12-13 12:32         ` Pierre Neidhardt
2019-12-13 12:32           ` Pierre Neidhardt

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='CAJ3okZ2m7oi-Pgz=xx+F5viLBV99-sVjBkx4g60zqYCTiFzvug@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=38455@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=mail@ambrevar.xyz \
    /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).