From: "Ludovic Courtès" <ludo@gnu.org>
To: "Tor-björn Claesson" <tclaesson@gmail.com>
Cc: 60640@debbugs.gnu.org
Subject: [bug#60640] Gnu: Add gdcm
Date: Tue, 17 Jan 2023 15:38:03 +0100 [thread overview]
Message-ID: <875yd5i5v8.fsf@gnu.org> (raw)
In-Reply-To: <87bkn1m4dj.fsf@gmail.com> ("Tor-björn Claesson"'s message of "Sat, 14 Jan 2023 19:06:29 +0200")
Tor-björn Claesson <tclaesson@gmail.com> skribis:
> From 9ec1adbf72f3b122a484fe449e3b950fcee4b221 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Tor-bj=C3=B6rn=20Claesson?= <tclaesson@gmail.com>
> Date: Sat, 14 Jan 2023 19:03:39 +0200
> Subject: [PATCH] gnu: gdcm: Add documentation.
>
> ---
> gnu/packages/bioinformatics.scm | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
[...]
> + "-DGDCM_DOCUMENTATION:BOOL=ON"
> + "-DGDCM_PDF_DOCUMENTATION:BOOL=ON"
> + (string-append "-DGDCM_INSTALL_DOC_DIR="
> + #$output:doc "/share/doc/" #$name)
> + "-DGDCM_BUILD_DOCBOOK_MANPAGES:BOOL=OFF"))) ; TODO: need ‘xsl-ns’
> + (native-inputs (list doxygen ghostscript graphviz texlive))
In general, we don’t install documentation as PDF/PS, unless there’s no
other choice (preferred formats are Info, man pages, and HTML).
Is there such an option?
Furthermore, we shouldn’t depend on ‘texlive’, which is the big
monolithic package:
https://guix.gnu.org/manual/devel/en/html_node/Using-TeX-and-LaTeX.html
Could you send an updated patch?
Ludo’.
next prev parent reply other threads:[~2023-01-17 14:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 19:40 [bug#60640] Gnu: Add gdcm Tor-björn Claesson
[not found] ` <handler.60640.B.167314095112989.ack@debbugs.gnu.org>
2023-01-08 7:59 ` [bug#60640] Acknowledgement (Gnu: Add gdcm) Tor-björn Claesson
2023-01-08 8:04 ` Tor-björn Claesson
2023-01-09 8:28 ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-09 10:50 ` Tor-björn Claesson
2023-01-10 7:01 ` ( via Guix-patches via
2023-01-10 14:40 ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-10 15:10 ` Tor-björn Claesson
2023-01-12 22:17 ` [bug#60640] Gnu: Add gdcm Ludovic Courtès
2023-01-13 10:45 ` Tor-björn Claesson
2023-01-13 23:50 ` Ludovic Courtès
2023-01-14 8:19 ` Tor-björn Claesson
2023-01-14 9:30 ` Tor-björn Claesson
2023-01-17 14:36 ` Ludovic Courtès
2023-01-14 17:06 ` Tor-björn Claesson
2023-01-17 14:38 ` Ludovic Courtès [this message]
2023-01-17 19:21 ` Tor-björn Claesson
2023-01-25 22:22 ` Ludovic Courtès
2023-01-20 11:30 ` Tor-björn Claesson
2023-01-20 12:44 ` Tor-björn Claesson
2023-01-25 22:01 ` Ludovic Courtès
2023-01-31 21:42 ` Tor-björn Claesson
2023-01-25 22:49 ` Ludovic Courtès
2023-01-27 15:06 ` Tor-björn Claesson
2023-01-14 19:34 ` Tor-björn Claesson
2023-01-14 21:58 ` Tor-björn Claesson
2023-01-10 14:52 ` Tobias Geerinckx-Rice via Guix-patches via
2023-01-11 5:29 ` Tor-björn Claesson
2023-01-12 11:21 ` Tor-björn Claesson
2024-02-19 22:41 ` bug#60640: " Sharlatan Hellseher
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=875yd5i5v8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60640@debbugs.gnu.org \
--cc=tclaesson@gmail.com \
/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.