Hyprland requires recent GCC/clang versions to work. Right now the approach is to have the logic behind that in pkg_setup, like this: ``` pkg_setup() { [[ ${MERGE_TYPE} == binary ]] && return if tc-is-gcc && ver_test $(gcc-version) -lt 14 ; then eerror "Hyprland requires >=sys-devel/gcc-14 to build" eerror "Please upgrade GCC: emerge -v1 sys-devel/gcc" die "GCC version is too old to compile Hyprland!" elif tc-is-clang && ver_test $(clang-version) -lt 18 ; then eerror "Hyprland requires >=sys-devel/clang-18 to build" eerror "Please upgrade Clang: emerge -v1 sys-devel/clang" die "Clang version is too old to compile Hyprland!" fi } ``` The ideal approach IMO would be to have the verison limits in BDEPEND. However I have gcc-13 and clang-18 installed with gcc being my primary compiler. Then that approach would allow me to compile when it shouldn't. That is why I propose adding a clang USE flag to the ebuild to allow for choosing the right compiler, like firefox does for example. That would add more flexibility, make the ebuild easier to work with. What do you think about it?
We don't really do this unless a package has real non-trivial requirements like Firefox does, and even then, we don't love it. I don't consider this case to warrant it. We're also going to stable GCC 14 soon (prep work is underway in bug 941869).
I see. Could you please explain/link to why the clang USE flag is not wanted?
https://devmanual.gentoo.org/general-concepts/use-flags/index.html#when-not-to-use-use-flags "You should not introduce USE flags that manipulate compiler flags or similar variables configured directly by the user (e.g. -O3, -flto). Instead, packages should avoid manipulating them at all, and let users set them directly."
