You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on my observation obs-service-cargo will generate .cargo/config.toml at the root of the project directory. This comes with some caveats that we have to do that --manifest-path=<path-to-Cargo.toml> as an additional flag on the specfile. This is not ideal.
If it's a workspace configuration, use the workspace Cargo.toml's location as the location for the .cargo/config.toml
Otherwise, we should put .cargo/config.toml for each location of the Cargo.toml for each crate found or used.
Relevant openSUSE package: monorepo-like Rust package such as python-tokenizers
Additionally, vendor seems to not extract at the exact path. Is this caused by the change when we merged a PR that modifies mtime in the tarball for reproducible builds
I remembered i designed this in a way where if it is extracted, they're extracted in the correct path... (i might be wrong so imma investigate this lol)
Based on my observation obs-service-cargo will generate .cargo/config.toml at the root of the project directory. This comes with some caveats that we have to do that --manifest-path=<path-to-Cargo.toml> as an additional flag on the specfile. This is not ideal.
So based on https://doc.rust-lang.org/cargo/reference/config.html#hierarchical-structure, I should
Relevant openSUSE package: monorepo-like Rust package such as python-tokenizers
I remembered i designed this in a way where if it is extracted, they're extracted in the correct path... (i might be wrong so imma investigate this lol)
TODO
The text was updated successfully, but these errors were encountered: