unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Florian Pelz <pelzflorian@pelzflorian.de>
To: 70333@debbugs.gnu.org
Cc: Florian Pelz <pelzflorian@pelzflorian.de>
Subject: [bug#70333] [PATCH 1/2] doc: contributing: Suggest building from Git.
Date: Thu, 11 Apr 2024 09:34:49 +0200	[thread overview]
Message-ID: <20240411073450.17958-1-pelzflorian@pelzflorian.de> (raw)
In-Reply-To: <20240411072114.16195-1-pelzflorian@pelzflorian.de>

* doc/contributing.texi (Requirements): Explain the purpose of
this section.  Refer regular contributors to Building from Git.

Change-Id: I731af4ac8e78b053b96a3b683528964223ab740b
---
 doc/contributing.texi | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index ad0f5a8ecd..cfe8b1289b 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -41,6 +41,14 @@ choice.
 @node Requirements
 @section Requirements
 
+You can easily hack on Guix itself using Guix and Git, which we use for
+version control (@pxref{Building from Git}).
+
+But when packaging Guix for foreign distros or when bootstrapping on
+systems without Guix, and if you decide to not just trust and install
+our readily made binary (@pxref{Binary Installation}), you can download
+a release version of our reproducible source tarball and read on.
+
 This section lists requirements when building Guix from source.  The
 build procedure for Guix is the same as for other GNU software, and is
 not covered here.  Please see the files @file{README} and @file{INSTALL}
-- 
2.41.0





  reply	other threads:[~2024-04-11  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  7:20 [bug#70333] [PATCH 0/2] Update Requirements section Florian Pelz
2024-04-11  7:34 ` Florian Pelz [this message]
2024-04-11  7:34 ` [bug#70333] [PATCH 2/2] doc: contributing: Move localstatedir instructions Florian Pelz
2024-04-26 10:07 ` bug#70333: [PATCH 0/2] Update Requirements section pelzflorian (Florian Pelz)

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=20240411073450.17958-1-pelzflorian@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=70333@debbugs.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).