From: Christoph Erhardt <fedora@sicherha.de>
To: linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Alejandro Colomar <alx.manpages@gmail.com>
Subject: Re: Is man-pages-posix redistributable?
Date: Thu, 29 Sep 2022 09:18:59 +0200 [thread overview]
Message-ID: <21618857.EfDdHjke4D@terra> (raw)
In-Reply-To: <cc7fc498-f068-9f62-967b-743805298ebb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Thanks, Alex!
I have reached out to The Open Group via some contact form on their website;
let's see if I'll get a reply from them.
On Wednesday, 28 September 2022 15:56:29 CEST Alejandro Colomar wrote:
> The person who could clarify this certainly is Michael Kerrisk. I'm not
> sure if he will have the time to read this, though.
>
> I'm sorry I have no idea. POSIX is too closed for my taste. I tried
> contacting them a long time ago regarding this, and I received no
> answer, and their website is a labyrinth to me.
>
> I encourage you to try to contact them with this problem, and ask that
> they clarify it, and if possible, that they publish the source code
> (hopefully the roff(7), not HTML) with whatever license they wish, so
> that I can pick it easily. I'm worried that if they don't do, I won't
> be able to provide manual pages for the next revision of POSIX, if they
> don't.
Hmm, that's a rather unsatisfying overall situation indeed. The description in
https://git.kernel.org/pub/scm/docs/man-pages/man-pages-posix.git/tree/README
is also vague on the details of how and where exactly to obtain the troff
sources.
I'd really like to get back to a state where I can successfully type
`man pthread_cond_wait` into a terminal on Fedora.
Best,
Christoph
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-29 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 6:14 Is man-pages-posix redistributable? Christoph Erhardt
2022-09-18 14:51 ` Christoph Erhardt
2022-09-28 8:15 ` Christoph Erhardt
2022-09-28 13:56 ` Alejandro Colomar
2022-09-29 7:18 ` Christoph Erhardt [this message]
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=21618857.EfDdHjke4D@terra \
--to=fedora@sicherha.de \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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.
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.