From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] man-pages-linux
Date: Thu, 30 Sep 2021 15:38:12 +0100 [thread overview]
Message-ID: <2bae97c6-53da-3c28-5859-cdf75fadb0ce@dronecode.org.uk> (raw)
In-Reply-To: <f3dfdffa-d3ed-f5d0-d2c3-2166b7b90386@SystematicSw.ab.ca>
On 28/09/2021 00:04, Brian Inglis wrote:
> I would like to provide Cygwin packages for the Linux kernel man pages
> project, for those who are concerned about interoperability and
> portability, from Michael Kerrisk (http://man7.org/), who also releases
> man-pages-posix, and recently released Linux man-pages 5.13.
>
> I do it for my own use anyway, to have the latest docs, just to save
> flipping to Linux from Cygwin or Windows.
>
> The install location is under the standard /usr/share/man/linux/ which
> can only by default be used by specifying
>
> $ man -m|--systems linux ...
>
> but can also be added explicitly to a users' MANPATH or alias e.g.
>
> $ alias man='man -m man,linux'
>
> or swap the order to prioritize Linux, or for parallel installs add each
> in your preferred order.
This is great. Go ahead.
I wonder if there's any scope for putting these pages in section
suffixed L or something e.g. 3L etc., so that pages could be found by
default for things which only exist on linux?
(But possibly that also requires some adjustment to the man configuration?)
Then I guess it would also be nice if a prologue similar to that of the
POSIX man pages (saying "this is the linux manpage, the cygwin
implementation may differ of be absent", could be added)
next prev parent reply other threads:[~2021-09-30 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 23:04 Brian Inglis
2021-09-30 6:05 ` Marco Atzeri
2021-09-30 14:38 ` Jon Turney [this message]
2021-09-30 16:06 ` Brian Inglis
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=2bae97c6-53da-3c28-5859-cdf75fadb0ce@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.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.
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).