Re: [ISSUE] [CLOSED] [RFC] Package multiple versions of llvm tool-chain

[github-actions [bot] <"github-actions [bot]"@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]

Closed issue by Calandracas606 on void-packages repository

https://github.com/void-linux/void-packages/issues/48222

Description:
<!--
  if you are creating a bug report or package request, please fill out one of the forms here:
  https://github.com/void-linux/void-packages/issues/new/choose

  Don't request an update of a package, We have a script for that:
  https://repo-default.voidlinux.org/void-updates/void-updates.txt
  However, a quality pull request may help.
-->

Major llvm releases introduce breaking changes, and it can take a while for software that depends on llvm to adapt.

Debian packages versioned llvm packages, as does llvm's own deb repository to allow multiple versions of the tool-chain to be installed simultaneously

Void already provides multiple versions of libllvm (12 and 15), I propose doing something similar but with more components of the tool-chain, such as clang and libclang.

For example, this would allow Void to build mesa with llvm17, but zig with llvm15 (zig does not support llvm17 yet)

This would also allow void to package new llvm versions, before setting one as the "default" versions. Similar to how void has "linux" and "linux-mainline" packages, void could add llvm17, but keep the llvm meta-package depending on llvm15. This would also require creating new meta-packages for other components of the tool-chain such as clang, and having the meta-package "clang" depend on a new package, "clang15".

llvm's cmake has support for building and installing in this way. /usr/bin/clang is already a symlink to /usr/bin/clang-15

If this seems reasonable, I propose adding these changes to my WIP llvm17 package, #46935