3 ms·
The article itself explicitly mentioning 'cargo vendor' (which, indeed, seems like the only logical choice for the kernel, just like they already do with zstd a
by mst 5y ago
The article itself explicitly mentioning 'cargo vendor' (which, indeed, seems like the only logical choice for the kernel, just like they already do with zstd as also mentioned in the article) leaves me extremely confused as to why people keep jumping to assuming non-vendored crate usage.
- sanderjd 5y agoIt seems like people don't know that it's possible? But obviously it's possible to pull dependency source code into the tree... The only question is whether or not there is tooling support for it. It could only possibly be a bonus to have something like cargo that can automate that workflow, rather than being forced to do it manually. So I agree, this particular criticism is very confusing. Though as I said, that doesn't mean no criticism is warranted!