Package Details: dxvk-winelib 1.4.4-1

Git Clone URL: https://aur.archlinux.org/dxvk-winelib.git (read-only)
Package Base: dxvk-winelib
Description: A Vulkan-based compatibility layer for Direct3D 10/11 which allows running 3D applications on Linux using Wine. Winelib version. Auto gets latest tag!
Upstream URL: https://github.com/doitsujin/dxvk
Licenses: zlib/libpng
Conflicts: dxvk, dxvk-git, dxvk-win32-git, dxvk-win64-git, dxvk-wine32-git, dxvk-wine64-git, dxvk-winelib-git
Provides: dxvk, dxvk-bin, dxvk-git, dxvk-mingw-git, dxvk-win32-git, dxvk-win64-git, dxvk-wine32-git, dxvk-wine64-git, dxvk-winelib-git
Submitter: nicman23
Maintainer: nicman23
Last Packager: nicman23
Votes: 0
Popularity: 0.000000
First Submitted: 2019-10-05 05:28
Last Updated: 2019-11-16 07:56

Pinned Comments

nicman23 commented on 2019-10-29 08:40

this package will never be out of date. it auto build the latest tag (but not master / random commits).

if the version is low that is because i have not bothered to update it, but it will be auto updated on build time (specifically on pkgver())

Latest Comments

nicman23 commented on 2019-11-16 12:03

i am not getting/ updating sources. metadata are not sources. if anything i am downgrading master to a stable tag, which itself is git running patch -R

FFY00 commented on 2019-11-16 09:08

What do you mean?

With this function, commands that are used to prepare sources for building are run, such as patching.

This is the place to prepare sources not to fetch/update them, like you are doing. The sources in sources are fetched and then prepare will move files, apply patches, etc. to make them suitable for the build process. You are updating the sources, when you should be preparing them.

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?

nicman23 commented on 2019-10-29 08:40

this package will never be out of date. it auto build the latest tag (but not master / random commits).

if the version is low that is because i have not bothered to update it, but it will be auto updated on build time (specifically on pkgver())