You are not logged in.
I've moticed that the scripts people have to use during install don't have manpages.
Some or most have -h, but it's quite natural to check for manpage first (after all, if -h
is not implemented, the script could do some unintended mess instead).
That's especially true considering they are bash scripts = more prone to such things.
In particular:
pacstrap
genfstab
arch-chroot
Also, manpage is missing for
archlinux-java
Just wondering if there's some policy not to document Arch scripts, or what's the deal.
Last edited by MightyPork (2015-08-10 05:51:15)
If it ain't broke, pacman -Syyu and it will be
Offline
I have never heard of such a policy. You are hereby cordially invited to write a man page and submit it as a bug report. I can only assume, that writing docs is work, and in my experience, people who write good software write horrible docs.
Offline
... and in my experience, people who write good software write horrible docs.
My experience is the opposite. The best developers produce the best documentation; certainly the more professional developers.. Often it is done almost effortlessly with tools like Doxygen.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Basic man pages could be generated from the --help output with help2man (in [extra]). Version has to be specified separately because they don't support --version. Example:
$ help2man -N --version-string=15 genfstab |man -l -
Add a Makefile target and it's "almost effortlessly"
Offline