From: "François J" <francois-oss@avalenn.eu>
To: 47968@debbugs.gnu.org
Subject: [bug#47968] [PATCH 1/2] gnu: git: add a comment on why we don't build manpages
Date: Fri, 23 Apr 2021 09:05:46 +0200 [thread overview]
Message-ID: <0849d63@noop.avalenn.eu> (raw)
In-Reply-To: <E1lZskH-0005Yn-3C@lists.gnu.org>
* gnu/packages/version-control.scm (git)[native-inputs]:
add back comment skipped by commit
d1cada0450fca54260fd20ab49d0586d147cbeb3
Signed-off-by: François J. <francois-oss@avalenn.eu>
---
gnu/packages/version-control.scm | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
index 3992f74644..fddabbcd40 100644
--- a/gnu/packages/version-control.scm
+++ b/gnu/packages/version-control.scm
@@ -188,6 +188,9 @@ as well as the classic centralized workflow.")
("bash" ,bash-minimal)
("bash-for-tests" ,bash)
("gettext" ,gettext-minimal)
+ ;; To build the man pages from the git sources, we would need a dependency
+ ;; on a full XML tool chain, and building it actually takes ages. So we
+ ;; use this lazy approach and use released tarball.
("git-manpages"
,(origin
(method url-fetch)
--
2.31.1
next prev parent reply other threads:[~2021-04-23 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 9:01 [bug#47968] [PATCH 0/2] Add git-filter-repo François J
2021-04-23 7:05 ` François J [this message]
2021-04-23 7:17 ` [bug#47968] [PATCH 2/2] gnu: " François J
2021-05-03 16:41 ` [bug#47968] [PATCH 0/2] " Ludovic Courtès
2021-04-23 7:17 ` [bug#47968] [PATCH] gnu: " François J
2021-05-03 20:46 ` bug#47968: [PATCH 0/2] " Ludovic Courtès
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=0849d63@noop.avalenn.eu \
--to=francois-oss@avalenn.eu \
--cc=47968@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 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.