unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Lilah Tascheter via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>, 57347@debbugs.gnu.org
Subject: [bug#57347] [PATCH] packages: Add man-pages-posix.
Date: Mon, 22 Aug 2022 22:33:59 -0500	[thread overview]
Message-ID: <20220823033359.2mzi7zxbjkg32ceo@pleiades> (raw)
In-Reply-To: <5c562c24-2a39-9b43-6c90-ef89724ac720@telenet.be>

On Tue, Aug 23, 2022 at 01:50:34AM +0200, Maxime Devos wrote:
> This package can easily be confused with 'man-pages' -- at least, I
> initially confused this as a duplicate of man-pages. Could the relationship
> be clarified in the description?
That's fair. How does this revised description sound? "Excerpts from the
POSIX.1-2008 and TC1 standards (collectively, POSIX.1-2013) in manual
page form. While the Linux man-pages project documents the system as it
exists, this package documents the portable software API nominally
implemented by many unix-likes."

> Maybe (assoc-ref %outputs "out") -> #$output and '(#:tests? ...) -> (list
> #:tests? #f #:make-flags #~(list ...) #:phases #~(...)), now we have G-exps.
Sounds good!

> Also, IIRC there's a #:make-target and #:parallel-build? #false
There is a #:parallel-build? #f, but no #:make-target field, as far as I
could tell. Though, the build phase doesn't explicitly target all, so it
would be possible to provide the gz target through #:make-flags.

But, also, all the build phase does is compress the manpages, which
could entirely be done by the compress-documentation phase with some
edits done to it; at the moment, its regex for detecting manpages
doesn't take into account the [023]p format of this package's manpages.

Thoughts?

> As a bonus, you could update the 'man-pages' package to the new G-exps,
> though not required.
Sure! I'll submit that with v2 as a patchset.

Thanks!
Lilah




  reply	other threads:[~2022-08-23 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 20:42 [bug#57347] [PATCH] packages: Add man-pages-posix Lilah Tascheter via Guix-patches via
2022-08-22 23:50 ` Maxime Devos
2022-08-23  3:33   ` Lilah Tascheter via Guix-patches via [this message]
2022-08-26 13:41     ` Maxime Devos
2022-08-27 23:37       ` [bug#57347] [PATCH v2 1/2] " Lilah Tascheter via Guix-patches via
2022-08-29 19:36         ` Maxime Devos
2022-09-08 12:55         ` bug#57347: [PATCH] " Ludovic Courtès
2022-08-27 23:37       ` [bug#57347] [PATCH v2 2/2] packages: Update man-pages package to newer style Lilah Tascheter via Guix-patches via
2022-08-23 13:08   ` [bug#57347] [PATCH] packages: Add man-pages-posix Lilah Tascheter via Guix-patches via

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=20220823033359.2mzi7zxbjkg32ceo@pleiades \
    --to=guix-patches@gnu.org \
    --cc=57347@debbugs.gnu.org \
    --cc=lilah@lunabee.space \
    --cc=maximedevos@telenet.be \
    /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).