LLVM 19 has been keyworded for a little while now (and has an essential PPC64 patch), and Chromium upstream is already building on LLVM 20. Please add a `0/llvm-19` subslot for Rust so that the Chromium ebuilds are able to depend on a more modern LLVM. If this is not possible, what alternative mechanisms are there for enforcing a 'Rust built with this LLVM' dependency? Do we need to do some eclass magic?
(In reply to Matt Jolly from comment #0) > LLVM 19 has been keyworded for a little while now (and has an essential > PPC64 patch), and Chromium upstream is already building on LLVM 20. For future reference that doesn't really matter, rust packaging uses the same version that upstream uses and that version only, and the current in-tree 1.81.1 uses llvm-18 so.. But as noted on IRC, rust-1.82.0 was released today a few hours ago and does newly use llvm19 now, so this is more of a bump request which is being worked on.
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=39f8f7408254 Author: Arthur Zamarin <arthurzam@gentoo.org> Date: Fri Oct 18 05:51:35 2024 virtual/rust: add 1.82.0