Open guihkx opened 5 months ago
Started test build 97853
Build 97853 failed
Thanks for finishing up and testing this!
My main concerns are actually about Flathub infrastructure.
barthalion is going to look into this at some point and will ensure that this transition can go smoothly.
Also marking as a draft to ensure no green buttons are accidentally hit.
Sync'd with master
.
Started test build 102118
Build 102118 failed
Sorry about the delay but barts been busy so it might be a while.
No worries at all, I completely understand.
I'm thinking of opening individual pull requests for some of the commits here, because some of them are fixing actual issues which are unrelated to the move off of extra-data
... 🤔
@TingPing Would that be okay with you?
@guihkx Sure go ahead.
@barthalion Is this still on your radar?
This is my take at solving #203, which is also pretty much a follow-up to #167.
Here are some pros of accepting this PR (in my opinion):
i386
build botAnd here are some potential cons (also in my opinion):
Overall slower build time: This issue is not directly related to the issue above (although this one can be worsened by it), Instead, it has to do with the fact that by switching from extra-data, Flathub now has to download 79 GiB worth of driver files every time a new driver version is added. A potential way mitigate this, would be by Flathub admins allocating ~100 GB of storage to cache all these installers, but this number will only grow with time... :(
Those things aside, I should also note that my testing capabilities are limited because I only have an old NVIDIA GPU, and so the actual testing of the driver was solely done with version 470.223.02.
In any case, I have wrote some instructions below for any contributors willing to build and test this locally.
Closes #42 Closes #156 Closes #203 Closes #217
How to build/package locally
1. Open
versions.sh
and edit theDRIVER_VERSIONS
variable at the very end, informing the versions you want to package, separated by a whitespace. For example, to package only the545.29.06
driver:2. Save the file. 3. Now simply invoke
make
to build forx86_64
(andi386
, simultaneously):4. After the build finishes, we can now create Flatpak bundles, so we can easily install the drivers later:
5. And then you can install them with:
Testing
Perhaps the easiest way to test this is by installing Flatpak'd Steam. Because Steam requires the
multiarch
permission by default, testing the 32-bit part of the driver is easier.My tests consist in downloading x86 and x86_64 binaries of
vulkaninfo
(to test Vulkan) andglxinfo
(to test OpenGL), and then running these two tools within thecom.valvesoftware.Steam
app, and observe that their output is correct.Below are command-line only instructions on how to do that.
Testing Vulkan (x86_64 / x86)
Testing OpenGL (x86_64 / x86)