Package Details: dxvk-winelib 1.6.1-6

Git Clone URL: https://aur.archlinux.org/dxvk-winelib.git (read-only, click to copy)
Package Base: dxvk-winelib
Description: Vulkan-based implementation of D3D9, D3D10 and D3D11 for Linux / Wine, Winelib version
Upstream URL: https://github.com/doitsujin/dxvk
Licenses: zlib/libpng
Conflicts: d9vk, dxvk
Provides: d9vk, dxvk, dxvk=1.6.1
Submitter: nicman23
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 3
Popularity: 0.000005
First Submitted: 2019-10-05 05:28
Last Updated: 2020-11-02 00:40

Latest Comments

« First ‹ Previous 1 2 3

nicman23 commented on 2019-11-16 07:57

As it is a custom license (it's not in the licenses package) it needs to be installed to the filesystem.

done

Don't submit the package then, it clearly does not follow the arch packaging guidelines which are to be used here in the AUR.

to be honest i cannot find anything in the wiki that the package breaks.. https://wiki.archlinux.org/index.php/Creating_packages#prepare() clearly states that you can patch the sources on the prepare function - which is what is git is, even if it is a reverse patch. It might be weird that nobody else is doing it but being novel is not breaking the rules. as for pkgver(), it also breaks no rules, as it just describes the source with the correct tag.

conflicts and provides

can you please help me with those. i edited them but i think this is not want you meant.

FFY00 commented on 2019-11-15 22:41

Oh, I also missed the license issue. As it is a custom license (it's not in the licenses package) it needs to be installed to the filesystem.

FFY00 commented on 2019-11-15 22:34

this is 100% for my use and i just uploaded it to the aur to be available for other people.

Don't submit the package then, it clearly does not follow the arch packaging guidelines which are to be used here in the AUR.

Other than this auto-updating trick the package is fine, if you don't want to maintain it I will just fix it and orphan the package.

yeah i ll fix that tomorrow, my bad.

No problem, if the other packages don't do that you should ask them to.

nicman23 commented on 2019-11-15 22:30

Please remove the prepare and pkgver routines

if it is an issue please submit a delete request. this is 100% for my use and i just uploaded it to the aur to be available for other people.

The way you are using provide/conflicts is also improper, this package should provide and conflict only dxvk

yeah i ll fix that tomorrow, my bad.

FFY00 commented on 2019-11-15 21:32

This is not how a PKGBUILD should behave. Please remove the prepare and pkgver routines. The way you are using provide/conflicts is also improper, this package should provide and conflict only dxvk. All of the other packages that provide dxvk should also do the same, this way you don't need to list every single package that provides dxvk in the PKGBUILD.

nicman23 commented on 2019-11-15 20:52

i do not want to have unencrypted ssh keys in my machine

eschwartz commented on 2019-11-15 20:50

If you want the package to stay up to date, why not just set up a cron job that regularly looks for a new tag, tries to bump and build the package, and commits the result if the build succeeded?