-
Thanks for App::cpangrep.
Could you make the dist produce the POD for cpangrep?
-
## Issue description
Man pages should be part of the derivation, not separate. The reason we have these is due to how we bootstrap Darwin. We can fix the bootstrapping to do this correctly.
-
It would be nice to rewrite the manpages in asciidoc and to build them using the [asciidoctor](https://asciidoctor.org/) gem. It's nicer to write in, and that would allow to have different output form…
-
Hi,
for the debian packaging, a manpage was written, but it makes sense to be included upstream (eventually needs updating)
-
```
I went through today and check for security related tools that lack manuals. I
found that not only do some lack manpages but they also lack usage help
(commonly --help). I even found one binary …
-
```
$ man frida-trace
No manual entry for frida-trace
```
-
```
I went through today and check for security related tools that lack manuals. I
found that not only do some lack manpages but they also lack usage help
(commonly --help). I even found one binary …
-
```
I went through today and check for security related tools that lack manuals. I
found that not only do some lack manpages but they also lack usage help
(commonly --help). I even found one binary …
-
Any interest in adding manpages from Arch?
-
with a README.md- > pod or a full --help it would be easier.
This pull request can not be automated.
```
cpan Markdown::Pod; markdown2pod README.md | pod2man > relexec.1
git add relexec.1; git commi…