diff options
| author | Matt Jolly <kangie@gentoo.org> | 2024-11-12 13:07:51 +1000 |
|---|---|---|
| committer | Matt Jolly <kangie@gentoo.org> | 2024-11-12 19:07:42 +1000 |
| commit | 34b74faa06a90bf9d4f62ecfca746b380d60517a (patch) | |
| tree | 2921fb46dc1b63bf48bb99594e0499b096906766 /dev-python/GitPython | |
| parent | 3d37ab7f493f626e059cd24b8de8b722ba53b30a (diff) | |
| download | gentoo-34b74faa06a90bf9d4f62ecfca746b380d60517a.tar.gz gentoo-34b74faa06a90bf9d4f62ecfca746b380d60517a.tar.bz2 gentoo-34b74faa06a90bf9d4f62ecfca746b380d60517a.zip | |
rust.eclass: revert simplified dependency simplification
The simplified dependency specification for cases where no RUST_MAX_SLOT
is set is the desired end state, however the edge case where portage
drops blockers with `--keep-going` has an unfortunate interaction where
both packages are installed simultaneously, e.g. dev-lang/rust-1.82.0:stable
and dev-lang/rust-1.82.0:1.82.0, and there's no easy way for end users
to resolve that as the legacy (though masked) ebuilds will meet the simple
Rust dependency.
Both packages install rlibs with different hashes in them to the same
path (as shown below) resulting in failures when a package attempts
to link against an rlib and finds two.
1.82.0: .../x86_64-unknown-linux-gnu/lib/libunwind-fc4fe814489209c6.rlib
1.82.0-r100: .../x86_64-unknown-linux-gnu/lib/libunwind-ab65e6747cbe4a5a.rlib
Bug: https://bugs.gentoo.org/943143
Bug: https://bugs.gentoo.org/943206
Signed-off-by: Matt Jolly <kangie@gentoo.org>
Diffstat (limited to 'dev-python/GitPython')
0 files changed, 0 insertions, 0 deletions
