cargo-ebuild
cargo-ebuild copied to clipboard
Make ebuild template configurable
Currently template is rather inflexible. We need to make in possible to load custom templates.
Once #10 lands we could provide default templates for:
- Crates that have system-dep in their deptree, we set the env-vars, add a dependency on pkg-config, potentially we came up with a list of external dependencies to match with the ebuild names. Here we could even autodetect it.
- Crates that use cargo-c to build C-libraries
- Crates that use clap
- Support autocompletion in one of the common ways
- Build manuals in one of the common ways
Do you know of other common patterns we could partially automate I'm forgetting of?