On Tue, 21 Apr 2026, Rhialto wrote:
The pkgsrc guide tells me to do this to update cargo-depends.mk (I started with an empty one): make CARGO_ARGS="build --release" build
No. You run "make show-cargo-depends > cargo-depends.mk" and that's it.
I am making a package because it tries to compile some C and it fails. We do have a package for that C library (mupdf-sys@0.6.0, from 2006 if we should believe the file dates!?!?) and it has some patches (print/mupdf/patches/patch-source_fitz_*). So either I need to copy the patches into this build (somehow), or (probably better) make it use the pkgsrc package for this.
You can make a patch for a vendor crate by making a patch for a file named ../vendor/<crate-name>/somefile. Check devel/cargo-c for an example.
Also, note that if the crate name ends in "-sys", that's supposed to be the same as "builtin" in pkgsrc. That is, it will probably check for an installed mupdf and only build its own bundled version if the builtin one is not acceptable.
-- Benny