From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Sergey Trofimov <sarg@sarg.org.ru>, 62228@debbugs.gnu.org
Cc: Bruno Victal <mirai@makinata.eu>
Subject: [bug#62228] [PATCH 1/2] gnu: Add halibut.
Date: Fri, 17 Mar 2023 08:50:32 +0100 [thread overview]
Message-ID: <b7e8791599f19e3bcc527142c611fefc6acb1108.camel@ist.tugraz.at> (raw)
In-Reply-To: <20230316212458.6187-1-sarg@sarg.org.ru>
Am Donnerstag, dem 16.03.2023 um 22:24 +0100 schrieb Sergey Trofimov:
> * gnu/packages/documentation.scm (halibut): New variable.
Split the cosmetic changes (prefixing guix licenses with license:) and
functional (adding halibut) changes into two: First the prefixing, then
adding halibut.
> +(define-public halibut
> + (package
> + (name "halibut")
> + (version "1.3")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (string-append
> +
> "https://www.chiark.greenend.org.uk/~sgtatham/halibut/halibut-"
> + version "/halibut-" version ".tar.gz"))
> + (sha256
> + (base32
> "0ciikn878vivs4ayvwvr63nnhpcg12m8023xv514zxqpdxlzg85a"))))
> + (build-system cmake-build-system)
> + (native-inputs (list pkg-config perl))
> + (arguments
> + '(#:tests? #f)) ; No tests.
Normally, arguments come after build-system and before any inputs.
> + (home-page
> "https://www.chiark.greenend.org.uk/~sgtatham/halibut/")
> + (synopsis "Documentation production system for software
> manuals")
> + (description "This is yet another text formatting system,
> intended primarily for
Use "Halibut" instead of "this". "yet another" is a little
superfluous.
> +writing software documentation. It accepts a single source format
> and outputs any or
> +all of text, HTML, Windows Help, man pages, GNU info, PostScript, or
> PDF.
any or all of => any combination of
text => plain text,
Windows Help => delete, we don't advocate unfree software here
man pages, GNU info => Unix man or info pages
I'd also add the word "document" to plain text, HTML, PostScript and
PDF. Feel free to regroup them.
Cheers
next prev parent reply other threads:[~2023-03-17 7:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 21:19 [bug#62228] [PATCH 0/2] gnu: Add sgt-puzzles Sergey Trofimov
2023-03-16 21:24 ` [bug#62228] [PATCH 1/2] gnu: Add halibut Sergey Trofimov
2023-03-16 21:24 ` Sergey Trofimov
2023-03-17 7:50 ` Liliana Marie Prikler [this message]
2023-03-17 13:15 ` Bruno Victal
2023-03-17 17:16 ` Liliana Marie Prikler
2023-03-16 21:25 ` [bug#62228] [PATCH 2/2] gnu: Add sgt-puzzles Sergey Trofimov
2023-03-17 3:05 ` Bruno Victal
2023-03-16 21:46 ` [bug#62228] [PATCH] " Sergey Trofimov
2023-03-17 7:40 ` [bug#62228] [PATCH v1] " Sergey Trofimov
2023-03-17 8:29 ` [bug#62228] [PATCH v2 1/3] gnu: Prefix licenses in documentation.scm Sergey Trofimov
2023-03-17 8:29 ` [bug#62228] [PATCH v2 2/3] gnu: Add halibut Sergey Trofimov
2023-03-17 8:29 ` [bug#62228] [PATCH v2 3/3] gnu: Add sgt-puzzles Sergey Trofimov
2024-03-10 21:36 ` [bug#62228] [PATCH v3 1/3] gnu: Prefix licenses in documentation.scm Sergey Trofimov
2024-03-10 21:36 ` [bug#62228] [PATCH v3 2/3] gnu: Add halibut Sergey Trofimov
2024-03-10 21:36 ` [bug#62228] [PATCH v3 3/3] gnu: Add sgt-puzzles Sergey Trofimov
2024-03-11 19:31 ` Liliana Marie Prikler
2024-03-11 19:31 ` [bug#62228] [PATCH v3 1/3] gnu: Prefix licenses in documentation.scm Liliana Marie Prikler
2024-03-12 7:28 ` [bug#62228] [PATCH v4 " Sergey Trofimov
2024-03-12 7:28 ` [bug#62228] [PATCH v4 2/3] gnu: Add halibut Sergey Trofimov
2024-03-12 7:28 ` [bug#62228] [PATCH v4 3/3] gnu: Add sgt-puzzles Sergey Trofimov
2024-03-12 7:50 ` Liliana Marie Prikler
2024-03-12 8:11 ` Sergey Trofimov
2024-03-12 16:47 ` [bug#62228] [PATCH v5 1/3] gnu: Prefix licenses in documentation.scm Sergey Trofimov
2024-03-12 16:47 ` [bug#62228] [PATCH v5 2/3] gnu: Add halibut Sergey Trofimov
2024-03-12 16:47 ` [bug#62228] [PATCH v5 3/3] gnu: Add sgt-puzzles Sergey Trofimov
2024-03-17 12:32 ` bug#62228: " Liliana Marie Prikler
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=b7e8791599f19e3bcc527142c611fefc6acb1108.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=62228@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mirai@makinata.eu \
--cc=sarg@sarg.org.ru \
/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).