diff options
| author | Eli Schwartz <eschwartz@gentoo.org> | 2024-07-12 11:27:23 -0400 |
|---|---|---|
| committer | Eli Schwartz <eschwartz@gentoo.org> | 2024-07-12 12:06:56 -0400 |
| commit | 92860b9146e02479dd67de74585f3d170f8c03e1 (patch) | |
| tree | f17893e6f32afe5670f2f61ed0d5f76d2dec1e87 /dev-python/GitPython/GitPython-3.1.43.ebuild | |
| parent | 90c9e42f05d28bfa7b3f6764594eaf6273d54260 (diff) | |
| download | gentoo-92860b9146e02479dd67de74585f3d170f8c03e1.tar.gz gentoo-92860b9146e02479dd67de74585f3d170f8c03e1.tar.bz2 gentoo-92860b9146e02479dd67de74585f3d170f8c03e1.zip | |
media-libs/mesa: update NVK rust crate handling to use meson packagecache
We do a bit of a song and a dance to slip rust crates into meson's
subprojects directory and migrate the meson.build files over. But meson
can handle this builtin via:
- `meson subprojects download`
- providing the tarball seeds in the packagecache and relying on
extraction at time of use
It's a bit less fragile than manual extraction because meson guarantees
that patch_directory handling is done and no need to manually
reimplement it in bash. The downside, for the moment, is that previously
the checksums didn't actually match what the meson wraps expected, due
to the differences between crates.io distfiles and github distfiles. So
we cannot rename the files on the mirror to what we want.
Once all the crate versions have been bumped by the passing of time, we
can rename them in SRC_URI and simply use ${MESON_PACKAGE_CACHE_DIR},
new since meson 1.3.0 (we already require 1.4 so that's okay), to tell
meson that it should use wrap tarballs from ${DISTDIR} without any
intervention.
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Diffstat (limited to 'dev-python/GitPython/GitPython-3.1.43.ebuild')
0 files changed, 0 insertions, 0 deletions
