Support installing manpages (and potentially other files)
*[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/cargo/issues/2729)* I use Cargo to build a command-line tool written in Rust. I've also written an accompanying manpage, `command.1`. I'd like to tell Cargo about manpages via Cargo.toml, so that `cargo install` will install them to the appropriate location (gzip-compressed and installed to `${root}/share/man/man1/command.1.gz`, where the section `1` in `man1` gets extracted from the first character of the manpage extension). Note that once Cargo has a mechanism for a post-build script, some packages may wish to use that to build the manpage. For instance, a package might parse `--help` output to generate a manpage, process some other document language to produce a manpage, or use help2man-like functionality from an argument parser. However, for a first pass, I'd just like to have support for installing manpages already written directly in manpage format.
Posted by joshtriplett on May 23, 2016, 2:56 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
Support installing manpages (and potentially other files)
*[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/cargo/issues/2729)* I use Cargo to build a command-line tool written in Rust. I've also written an accompanying manpage, `command.1`. I'd like to tell Cargo about manpages via Cargo.toml, so that `cargo install` will install them to the appropriate location (gzip-compressed and installed to `${root}/share/man/man1/command.1.gz`, where the section `1` in `man1` gets extracted from the first character of the manpage extension). Note that once Cargo has a mechanism for a post-build script, some packages may wish to use that to build the manpage. For instance, a package might parse `--help` output to generate a manpage, process some other document language to produce a manpage, or use help2man-like functionality from an argument parser. However, for a first pass, I'd just like to have support for installing manpages already written directly in manpage format.
Comments (0)
No comments yet. Start the discussion.