feat: amdvlk, directxshadercompiler
Aims to fulfill package request #2070. Discussion (more of a monologue) on some key issues I have with both the proposal itself and my current implementation of it will be provided below in comments.
- AMDVLK already provides their builds of the driver for RHEL/as an RPM, so is this package really needed?
- DirectXShaderCompiler
- (by default) Should we build with external libraries or with libraries from Fedora's repositories?
AMDVLK already provides their builds of the driver for RHEL/as an RPM, so is this package really needed?
Specifically on this topic: ~~I believe that the upstream's specfile~~ could be used instead if we don't trust the upstream-provided binaries. Alternatively, could AMDVLK be somehow shipped as the upstream-provided package?
Edit 1: Upstream does not provide a specfile and instead uses CPack to create the package.
we (fyra) are having an ongoing discussion on whether we allow shipping upstream-provided rpms directly, but before we draw a conclusion I think it's not a bad idea to just provide our own rpms anyway
AMDVLK is dead, long live RADV
https://www.phoronix.com/news/AMDVLK-Discontinued
AMDVLK is dead, long live RADV
https://www.phoronix.com/news/AMDVLK-Discontinued
While that is true, some video and other editing software do not accept or work with Mesa. It's a frustrating situation.