summaryrefslogtreecommitdiff
path: root/dev-lang/rust-bin/rust-bin-9999.ebuild
diff options
context:
space:
mode:
authorSam James <sam@gentoo.org>2025-10-20 23:53:06 +0100
committerSam James <sam@gentoo.org>2025-10-20 23:55:01 +0100
commit25baf2a66c5e0b0b08094573aa74031a103bea08 (patch)
tree08ea9515d4c955bb09c0c8426767b2d45d3c46c6 /dev-lang/rust-bin/rust-bin-9999.ebuild
parent4971d9452de54f00a83d5a484b1b7713a2b76cba (diff)
downloadgentoo-25baf2a66c5e0b0b08094573aa74031a103bea08.tar.gz
gentoo-25baf2a66c5e0b0b08094573aa74031a103bea08.tar.bz2
gentoo-25baf2a66c5e0b0b08094573aa74031a103bea08.zip
dev-lang/rust: don't try to delete new JSON target file
etc/target-spec-json-schema.json now gets installed by Rust but gets caught by the sanity check we have for cleaning up bash-completion (which gets handled by dev-lang/rust-common). It's now expected to have something left in etc/, so cleanup the rmdir accordingly to just kill the bash-completion dir. Note that this JSON file doesn't seem appropriate for rust-common because: 1) it's generated (so would require us to build something to install it); 2) per the commit introducing it: > Because the schema is subject to change, you should always use the schema > from the version of rustc which you are passing the target to. > > The existence and name of this schema is, just like the properties of the > JSON specification, not stable and subject to change. Closes: https://bugs.gentoo.org/964416 Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-lang/rust-bin/rust-bin-9999.ebuild')
0 files changed, 0 insertions, 0 deletions