On 2018/12/14 17:53, Charles A Daniels wrote: > As a short aside, enumerating all the dependencies was a massive pain. > Has there been any work done on at least partially automating generation > of Cargo ports?
It is already partially automated, see port-modules(5) about the make targets added by the devel/cargo module (and see the module itself, devel/cargo/cargo.port.mk, for more comments and how it works). quick comments on Makefile - missing "# $OpenBSD$" at the top, and : COMMENT = A fast CSV command line toolkit written in Rust. in common with other ports, skip the indefinite article and trailing full stop, and the language isn't really relevant for something that isn't a library/module - usual style would be more like e.g. "fast CSV command-line toolkit". (also there is a stray blank line at EOF in pkg/DESCR). Someone more familiar with rust porting probably knows more but IIRC the WANTLIB in ripgrep is to slightly reduce the risk of missing packages getting updated after a change in base, probably worth having, but manual bumps are often needed anyway. (go and rust's attempts to provide "static" binaries are only really valid on OS which have a fossilized ABI..)
