https://rust-lang-nursery.github.io/cli-wg/ – tracking repo: https://github.com/rust-lang-nursery/cli-wg/issues
spacekookie on master
Clarify source position Make i… (compare)
rustspl
https://www.reddit.com/r/rust/comments/agmpts/my_first_useful_rust_program_misspell_any/?st=jra2cf4b&sh=b67e2920
Didn't realize its a port of go.
Not Rust specific. I've been wanting this at $DAYJOB for a mostly C++/Python code base
CLI question for y'all: I'm working on improving the docs for man
and want to be able to tell users what the best way to generate/install a man page is…which makes me realize I don't know. What is the best way to generate/install a man page using man
?
man
works really well with a build.rs
script, which seems like the best way to generate a man page. But then the generated page will be in ./target/release/build/<APP_NAME-HASH>/out
directory. Is there a good cross-platform way to access that output file, given that we don't know the hash? I'm guessing we should recommend people use a makefile
plus some POSIX-compatible command to find the file—does that seem right? If so, any ideas what the command would be?
In the future, stager might be able to help because it will be invoking cargo and we might be able to set it up so some relative path stuff could work.
Otherwise, I'm tempted to say to have a second binary meant for generating assets like this (completions are another one)
build.rs
is grabbing all the relevant logic. For cargo-tarball
I've started off using build.rs
but I might move away from it in the future because any file my args.rs
touches also has to be included