Glad you like the package and thanks for the alert aviallon.
Let's assume that I used llvm / clang /llvm-libs without a version number in dependencies.
(You = mesa-git user)
This will work fine UNTIL archlinux repos are updated to a new llvm version.
You upgrade the system, reboot or login to X : black screen because the llvm-libs version needed by mesa-git is no longer present
.
You investigate, post here, post on forum until the solution is found : rebuild mesa-git against the new llvm .
Depending on a specific llvm version prevents this by blocking the llvm upgrade and requiring manual action before the llvm upgrade can go through.
Pinned Comments
Lone_Wolf commented on 2021-01-03 15:38
I am using another package now and am looking for a new maintainer.
Lone_Wolf commented on 2020-04-23 12:26
Mesa and llvm are closely tied together. Everytime the llvm mesa is built against changes/updates , mesa needs to be rebuilt.
I expect anyone building mesa-git against one of the llvm trunk variants to be able to do that themselves, but atleast some of the people that built against repo llvm don't understand how to deal with such a rebuild.
The rest of this post is meant for those people.
Option A - best one
see https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot for the official way or https://aur.archlinux.org/packages/clean-chroot-manager for an alternative method.
Option B - 2nd best
Lone_Wolf commented on 2019-07-09 13:43
Why would I want to use llvm development versions ?
AUR helpers like yay and pamac can't deal with such a dynamic choice. People who use those will have to accept the default of building mesa-git against stock repo packages.
Lone_Wolf commented on 2018-01-30 14:06
run pacman Syu update non-repo packages for llvm if you use them
build mesa-git, log out , restart X .
run glxinfo to verify basic OpenGL functionality
build lib32-mesa-git
run glxinfo32 to verify basic OpenGL functionality for multilib programs