Will Page

> Changing this will break backwards-compatibility. I work with projects that rely on this behavior to easily inject configuration into `cargo` without modifying the source directory (by simply invoking cargo...

> At this point, I think that the current behavior of `--manifest-path` is actually correct. The `.cargo/config.toml` file controls the behavior of cargo itself, it's not crate configuration, and so...

Let me tell you, it was no fun to track down that issue, because the panic message was getting swallowed, and the exhausted filehandles meant that human-panic couldn't write a...

I notice that you do some patching of the build. I personally encountered some build errors and had to make some changes in order to get it to build on...

Relatedly, and I can move this into a separate issue if you'd like, is how to build/start in profiling mode. I have a bundle that I built with --profile, but...

I've made a go at cross compiling those myself, but failed miserably at every turn (llvm was a pain, but I got it built, but I never succeeded at getting...

IANAL & TINLA (I am not a lawyer and this is not legal advice), but I am a corporate copyright and licensing facilitator. @hmvp has a point. Ideally, the LICENSE-MIT...

I got minimal.pdf from [this site](https://brendanzagaeski.appspot.com/0004.html), which documents in detail the structure of their minimal pdf.

The note about the trailing slash under "additional information" is in question. Subsequent retesting seems to suggest something else is going on. I am continuing to look into it.

> @compenguy would bitbake be able to take advantage of [`cargo --config `](https://doc.rust-lang.org/cargo/reference/unstable.html#config-cli) which looks like it'll be released in 1.63? It's a really weird fit. The meta-build system (in...