From: Ingo Schwarze <schwarze@usta.de>
To: Alejandro Colomar <alx@kernel.org>, Michael Vetter <jubalh@iodoru.org>
Cc: linux-man@vger.kernel.org, groff@gnu.org
Subject: Re: groff in openSUSE
Date: Fri, 25 Aug 2023 16:31:53 +0200 [thread overview]
Message-ID: <ZOi7WeZcJUxuPokX@asta-kit.de> (raw)
In-Reply-To: <961d519a-78d3-25e3-dde8-75d5e0e2fe16@kernel.org>
Hi Michael,
Alejandro Colomar wrote on Fri, Aug 25, 2023 at 02:56:15PM +0200:
> On 2023-08-25 14:05, Michael Vetter wrote:
>> # conflicts with mandoc
>> mkdir man7mp
>> mv man7/man.7 man7mp/man.7mp
Creating a subdirectory for the Linux Man Pages Project sounds
like a bad idea to me. I would expect that to confuse users
because the Linux Man Pages Project is arguably the most important
documentation on Linux, so relegating even part of that to a
subdirectory feels at least surprising.
> Since you use man-db as your primary man(1) implementation --or I
> thought you do--, having man(7) provided by mandoc makes no sense.
> You should have groff's groff_man(7) be your man(7) --maybe via a
> link page (.so), or via a symlink--.
As the upstream maintainer of the mandoc(1) toolkit, i concur.
The man(7) manual page included in the mandoc toolkit documents
how mandoc implements the man(7) language. That is only useful
for operating systems regarding man(7) as an obsolete historical
language, which isn't the case for Linux because Linux still
sticks to the 1979 tradition of using man(7) for most manual pages
and even supports writing new manual pages in man(7) - even though
i understand that Alejandro is now also willing to accept new
manual pages written in the younger mdoc(7) language which is more
powerful, easier to write, and less susceptible to compatibility
problems nowadays.
If you want to install the mandoc version of the man(7) manual page
on openSUSE - which may occasionally be useful for very experienced
manual page users on openSUSE who wonder what exactly mandoc implements -,
you should probably pick a different name like mandoc_man(7) by
assigning to the MANM_MAN configuration variable in configure.local
as documented in configure.local.example, for example by adding a
line similar to this to configure.local:
# Some distributions may want to avoid naming conflicts among manuals.
# If you want to change the names of installed section 7 manual pages,
# the following alternative names are suggested.
# The suffix ".7" will automatically be appended.
# It is possible to set only one or a few of these variables,
# there is no need to copy the whole block.
MANM_MAN="mandoc_man" # default is "man"
Yours,
Ingo
--
Ingo Schwarze <schwarze@usta.de>
http://www.openbsd.org/ <schwarze@openbsd.org>
http://mandoc.bsd.lv/ <schwarze@mandoc.bsd.lv>
prev parent reply other threads:[~2023-08-25 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4a600a55-a68c-1c7a-42cb-403e2f51aed0@kernel.org>
[not found] ` <2c5edf3e-9e8a-fa7e-410b-8b805bd97461@iodoru.org>
2023-08-25 12:56 ` groff in openSUSE Alejandro Colomar
2023-08-25 14:31 ` Ingo Schwarze [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=ZOi7WeZcJUxuPokX@asta-kit.de \
--to=schwarze@usta.de \
--cc=alx@kernel.org \
--cc=groff@gnu.org \
--cc=jubalh@iodoru.org \
--cc=linux-man@vger.kernel.org \
/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