unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: gwl-devel@gnu.org
Cc: Kyle Meyer <kyle@kyleam.com>
Subject: [PATCH] HACKING: Use .guix.scm in 'guix environment' snippet
Date: Sat,  8 Feb 2020 12:05:23 -0500	[thread overview]
Message-ID: <20200208170523.11212-1-kyle@kyleam.com> (raw)

* HACKING (Development environment): Simplify the 'guix environment'
snippet by passing the existing .guix.scm to --load rather than
manually listing inputs.

Aside from being less of a mouthful, an advantage of doing this is
that the inputs need to be maintained in only a single spot, avoiding
the list in HACKING becoming stale (as is the case right now because
guile-gcrypt and guile-pfds are missing).  The downside to using
.guix.scm is that it will also bring in texlive-tiny and graphviz,
which are required only for 'make distcheck'.
---
 HACKING | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/HACKING b/HACKING
index 7ceb1b6..2e24297 100644
--- a/HACKING
+++ b/HACKING
@@ -13,10 +13,7 @@ Copyright © 2018 Ricardo Wurmus <rekado@elephly.net>
 You can use Guix to set up a development environment:
 
 #+BEGIN_SRC shell
-guix environment --ad-hoc \
-  autoconf automake pkg-config \
-  texinfo \
-  guile@2.2 guile-commonmark guile-wisp guile-syntax-highlight
+guix environment --load=.guix.scm
 #+END_SRC
 
 * Commit access

base-commit: af9e6f66144d6bb1ca19a24cf213bf04ef0317a3
-- 
2.25.0

             reply	other threads:[~2020-02-08 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-08 17:05 Kyle Meyer [this message]
2020-02-08 17:20 ` [PATCH] HACKING: Use .guix.scm in 'guix environment' snippet Kyle Meyer
2020-02-08 18:12 ` Ricardo Wurmus

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://www.guixwl.org/

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

  git send-email \
    --in-reply-to=20200208170523.11212-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=gwl-devel@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.
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).