Re: Mesa vulkan layer path fix for core-updates

[Kaelyn <kaelyn.alexi@protonmail.com>]

------- Original Message -------
On Wednesday, April 19th, 2023 at 3:26 PM, Andreas Enge <andreas@enge.fr> wrote:


> 
> 
> Hello,
> 
> thanks for bringing this back to our attention!

You're welcome! :)

> 
> Am Wed, Apr 19, 2023 at 02:41:57PM +0000 schrieb Kaelyn:
> 
> > While I know it is late in the process of preparing core-updates for merging into master, I wanted to ask if it would be possible to have the patch addressed prior to the merge?
> 
> 
> Given how many packages depend on mesa and their importance, I think it
> would be safer to postpone the fix until after the merge; be it in a
> dedicated mesa feature branch that could quickly be merged afterwards,
> or better yet regroup other changes in this area. (Searching for open mesa
> packages on issues.guix.gnu.org returns quite a few matches, this could be
> a good occasion to sort them out.)

I'm okay with it waiting until after the core-updates merge and going into a feature branch, especially if that branch includes updating mesa to the latest release (currently 23.0.0, or 22.3.7 if going with the latest patch of the previous feature release instead of the x.y.0 release of the newest series).

Inspired by your comment, I also just did a quick scan of https://issues.guix.gnu.org/search?query=mesa+is%3Aopen and took a peek at some tickets that looked like they may be related to the mesa package. From that perspective, six other tickets caught my eye in the results:

* https://issues.guix.gnu.org/62176 can be closed when core-updates is merged, since core-updates contains mesa 22.2.4

* https://issues.guix.gnu.org/58887 looks like an alternate way of solving the layer path issues that https://issues.guix.gnu.org/59453 also addresses. Additionally, it adds two new nonstandard VK_*_PATH variables to vulkan-loader, with at least VK_ILAYER_PATH seeming very similar in functionality to VK_LAYER_PATH and VK_ADD_LAYER_PATH described at https://github.com/KhronosGroup/Vulkan-Loader/blob/main/docs/LoaderInterfaceArchitecture.md

* https://issues.guix.gnu.org/58251 would be fixed by https://issues.guix.gnu.org/59453

* https://issues.guix.gnu.org/62313 might need a modification to mesa e.g. to add VDPAU_DRIVER_PATH as a native-search-path (one possible solution; in my home profile I made VDPAU work by setting "VDPAU_DRIVER_PATH=/run/current-system/profile/lib/vdpau").

* https://issues.guix.gnu.org/48868 appears to be the same VDPAU_DRIVER_PATH issue as https://issues.guix.gnu.org/62313.

* Though not exactly mesa-related, https://issues.guix.gnu.org/61364 can possibly be closed now, and almost certainly once the core-updates merge is completed. (The ticket is a number of workarounds the user applied in early Feb to be able to build their system profile using core-updates, to pick up Mesa 22 for newer hardware support. I'm not sure if any of the patches are still relevant.)

Cheers,
Kaelyn