I guess another way to use
cargo template could be to co-opt an example and rewrite the name and dependencies in the Cargo.toml. It could be
cargo template clone tokio/hello-world. But, as @withoutboats pointed out, examples don't have Cargo.toml files.
I'm not sure think this is even needed. We know the name because it's on the cmd line. We know the author because it's in the git or hg config (or overridden using
--author). Indeed the only thing left is the templated_paths to set the date in the LICENSE and/or README.
I'm still not sold on using crates.io for this. I'm with @ssokolow here that I would give preference to the local filesystem. I like the debian/ubuntu style
sources.list, which is what inspired the
CargoTemplates.toml mentioned above but maybe that's a hassle for people to add a new source each time they want to try a new template.
Maybe if we use
crates:// as a custom URL scheme? I'm not an IETF-type-person so I don't know how frowned upon custom URL schemes are. I defer to any Mozillan here.