From: Alejandro Colomar <alx.manpages@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: linux-man@vger.kernel.org,
"G . Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Linux man-pages Makefile portability
Date: Thu, 21 Jul 2022 16:17:18 +0200 [thread overview]
Message-ID: <fdde7402-5e69-b6ff-60fc-74ad9c9054f1@gmail.com> (raw)
In-Reply-To: <6e294373-2661-286c-09c4-e67cd84103d7@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1827 bytes --]
Hi Ingo!
On 7/3/22 23:44, Alejandro Colomar wrote:
> [added Branden, as he was involved in discussions regarding man3type;
> Branden, you might want to visit this thread from the begining, as I
> only copied the minimum to reply; it's in linux-man@]
>
> On 6/20/22 15:49, Ingo Schwarze wrote:
[...]
>> That said, other projects are of course free to have such pages if
>> they want to. The mandoc(1) program is also able to handle paths like
>> "man3/id_t.3type". It will consider that page to be *both* in section
>> "3" (as specified by the directory name) and in section "3type" (as
>> specified by the file name and by the .TH macro). I would consider
>> it better style to keep section names consistent, i.e. to use either
>> "man3/id_t.3" .TH id_t 3 or "man3type/id_t.3type" .TH id_t 3type,
>> but it's not a big deal: since many systems (in particular various
>> Linux distros) suffer from such inconsistencies, handling such
>> inconsistencies gracefully is an important feature that certainly
>> won't get removed.
>
> I considered[6] using man3type, and used man3 in the end just because
> when in doubt I opted for the smallest change. Knowing that it breaks
> mandoc(1), I'll definitely move to <man3type/>.
>
> [6]:
> <https://lore.kernel.org/linux-man/761bb12f-31e0-369d-8315-d2e1545505c7@gmail.com/T/#u>
>
I fixed it:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=451a27a78d51973b01bfb5d3b1e0ec081d9161e1>
And Debian seems to work fine with man3type/ and man2type/ out of the
box, so I prefer it this way. I hope that other projects follow the
example; and that packagers/distributions also create subsection
directories, and don't undo my work.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-21 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 17:52 Linux man-pages Makefile portability Alejandro Colomar
2022-06-19 21:06 ` Ingo Schwarze
2022-06-19 22:23 ` Alejandro Colomar
2022-06-20 13:49 ` Ingo Schwarze
2022-07-03 21:44 ` Alejandro Colomar
2022-07-21 14:17 ` Alejandro Colomar [this message]
2022-07-22 16:59 ` Ingo Schwarze
2022-07-22 17:37 ` Alejandro Colomar
2022-07-23 18:16 ` Ingo Schwarze
2022-07-24 11:09 ` Alejandro Colomar (man-pages)
2022-07-24 15:57 ` Ingo Schwarze
2022-07-24 17:29 ` Semantic man(7) markup (was: Linux man-pages Makefile portability) G. Branden Robinson
2022-07-24 21:26 ` Ingo Schwarze
2022-07-25 9:28 ` Linux man-pages Makefile portability Colin Watson
2022-07-25 12:46 ` bash-completion doesn't support man subsections (was: Linux man-pages Makefile portability) Alejandro Colomar
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=fdde7402-5e69-b6ff-60fc-74ad9c9054f1@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=schwarze@usta.de \
/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 NNTP newsgroup(s).