From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>, Stefan Puiu <stefan.puiu@gmail.com>,
Jakub Wilk <jwilk@jwilk.net>, lnx-man <linux-man@vger.kernel.org>
Subject: Move man* to man/ (was: Revert 70ac1c478 ("src.mk, All pages: Move man* to man/"))
Date: Tue, 26 Mar 2024 02:28:59 +0100 [thread overview]
Message-ID: <ZgIk4mN4bXfsiiYy@debian> (raw)
In-Reply-To: <Yxr9WN7f3FEqKVRg@pevik>
[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]
Hi,
I'm thinking of adding some features to the build system that would need
having a clean man/ directory. The main one is building several books
for other projects, one per language, where languages correspond to
every directory within man/ that doesn't match man*. Currently, I'm
workarounding this by running the build system several times, for each
language dir, but it could be much simpler, I think.
For not having a regression in the number of characters one needs to
type to edit the manual pages, I thought of adding symlinks in the root
of the repository, so it would look like this:
$ ls -l man*
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man1 -> man/man1/
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man2 -> man/man2/
lrwxrwxrwx 1 alx alx 13 Mar 26 02:25 man2type -> man/man2type/
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man3 -> man/man3/
lrwxrwxrwx 1 alx alx 14 Mar 26 02:26 man3const -> man/man3const/
lrwxrwxrwx 1 alx alx 13 Mar 26 02:26 man3head -> man/man3head/
lrwxrwxrwx 1 alx alx 13 Mar 26 02:26 man3type -> man/man3type/
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man4 -> man/man4/
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man5 -> man/man5/
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man6 -> man/man6/
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man7 -> man/man7/
lrwxrwxrwx 1 alx alx 9 Mar 26 02:26 man8 -> man/man8/
man:
total 120
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man1
drwxrwxr-x 2 alx alx 20480 Mar 26 02:24 man2
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man2type
drwxrwxr-x 2 alx alx 57344 Mar 26 02:24 man3
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man3const
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man3head
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man3type
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man4
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man5
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man6
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man7
drwxrwxr-x 2 alx alx 4096 Mar 26 02:24 man8
What do you think about it?
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-26 1:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 9:41 Revert 70ac1c478 ("src.mk, All pages: Move man* to man/") Petr Vorel
2022-09-06 11:19 ` Alejandro Colomar
2022-09-06 11:57 ` Alejandro Colomar
2022-09-06 11:58 ` Alejandro Colomar
2022-09-06 16:09 ` Petr Vorel
2022-09-07 20:53 ` Jakub Wilk
2022-09-07 22:11 ` Alejandro Colomar
2022-09-08 12:42 ` Stefan Puiu
2022-09-09 8:46 ` Petr Vorel
2022-09-15 13:40 ` Alex Colomar
2022-09-15 13:48 ` Petr Vorel
2023-08-02 21:38 ` Alejandro Colomar
2023-08-02 21:45 ` Alejandro Colomar
2024-03-26 1:28 ` Alejandro Colomar [this message]
2024-04-26 12:43 ` Ping: Re: Move man* to man/ (was: Revert 70ac1c478 ("src.mk, All pages: Move man* to man/")) Alejandro Colomar
2024-04-26 18:03 ` Petr Vorel
2024-04-26 20:19 ` 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=ZgIk4mN4bXfsiiYy@debian \
--to=alx@kernel.org \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=stefan.puiu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox