Conversation
|
This package/branch should be buildable against this PR: https://github.com/kgilmer/elbey/tree/experiment/vendored-debian-pkg |
|
I want to change the detection to presence of the cargo checksum file, other cleanup |
|
this is ready for a pass when you have time @khos2ow |
khos2ow
left a comment
khos2ow
left a comment
There was a problem hiding this comment.
I have completely missed this PR!! Sorry. A question below, otherwise LGTM, in terms of the green pipeline.
| [ -d vendor ] && rm -rf vendor | ||
| rm -rf Cargo.lock || true | ||
| cargo vendor | ||
| tar Jcf ../${debian_package_name}_${debian_version}.orig-vendor.tar.xz vendor/ |
There was a problem hiding this comment.
I see, in the blog post, that new stanza is added in rules, but I don't get how does this tarball being used? Do we also need to push this tarball to deb archive?
There was a problem hiding this comment.
This feature requires an integration on the package side. In the build script of a rust package we'd like to "autovendor", we update the cargo configuration to include the packages. See here for the example that was tested:
There was a problem hiding this comment.
I added some basic docs, please LMK if there is still ambiguity or questions
2 participants
Using vendoring technique described at https://blog.shadura.me/2020/12/22/vendoring-rust-in-debian-derivative/
This change is to enable building/packaging Rust programs that do not have (all) dependencies already in Debian. This will cause cargo to dowload all dependency source and provide it to the Debian builder's version of the cargo repo.