It seems the patches are what makes the compilation fail, probably because 2.80 is such a big update. I tried to comment the patches and it's compiling right now, will update if everything compiles fine.

While it compiles, @kyrios123 do you remember what were the patches for? If it passes compilation without them does that mean we can just not include them or are they needed so blender functions properly?

@Tzigamm

About the purpose of a patch
If there is no comment in the patch or package.yml and the patch name is not self-explaining, please reffer to the corresponding commit message to get more details

About failing patches
When a patch fails to apply, just look at the code main causes are

• patch has been merged upstream
• patch need to be rebased
• code has been deeply refactored (usually such changes are mentionned in the News/Changelog/Release notes)

PS: You can look at the .rej file to get the details about the rejections if necessary.

Thanks a lot kyrios! So apparently Blender can compile without the patches (or at least compile enough to give me an error) but it gives an error about the python3 version, so we need to update python3 before blender.

As stated in T6817 it won't be an easy task and probably will take a while so if someone needs Blender 2.8in the meantime they should use the distro agnostic version given by the BF here.

For what it's worth, you can also download Blender 2.80 through Steam, as an alternative to directly downloading from the Blender Foundation.

I'd be willing to handle this as I more or less maintain Blender 2.8x for Exherbo too.

@ermo take it in your basket if you want!
I did the update just because I know it's a long awaited update and I wanted to improve the package.yml a little.