That .SRCINFO thing also causes yay (a AUR helper) to always detect this package as an upgrade, even though the latest version is already installed.
Search Criteria
Package Details: dxvk-bin 2.3.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/dxvk-bin.git (read-only, click to copy) |
---|---|
Package Base: | dxvk-bin |
Description: | A Vulkan-based compatibility layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine (Windows DLL binary files) |
Upstream URL: | https://github.com/doitsujin/dxvk |
Keywords: | dxvk |
Licenses: | zlib/libpng |
Conflicts: | d9vk, dxvk |
Provides: | d9vk, dxvk |
Submitter: | ssorgatem |
Maintainer: | ssorgatem (kekonn) |
Last Packager: | kekonn |
Votes: | 222 |
Popularity: | 2.10 |
First Submitted: | 2018-03-02 07:39 (UTC) |
Last Updated: | 2024-04-16 17:51 (UTC) |
Dependencies (2)
- vulkan-icd-loader (vulkan-icd-loader-gitAUR)
- lib32-vulkan-icd-loader (lib32-vulkan-icd-loader-gitAUR) (optional) – 32-bit Windows application support
Required by (6)
- aio-creator-neo (requires dxvk)
- arch-gaming-meta (optional)
- d8vk-bin (requires dxvk)
- dxvk-nvapi-mingw (requires dxvk)
- dxvk-nvapi-mingw-git (requires dxvk)
- gaming-lutris-steam-nvidia
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 16 Next › Last »
gamezelda commented on 2019-09-22 15:33 (UTC)
ssorgatem commented on 2019-09-22 08:16 (UTC)
That's weird, I sure haven't touched .SRCINFO at ll after generating with makepkg --printsrcinfo
kode54 commented on 2019-09-22 06:32 (UTC)
.SRCINFO
also appears to have been hand edited rather than auto generated, it says the package version is 1.4.0
, while the PKGBUILD
says it's 1.4
.
UnicornDarkness commented on 2019-09-20 05:15 (UTC)
@ssorgatem: pkgrel
should be 1, not 0. https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel
UnicornDarkness commented on 2019-09-14 08:13 (UTC)
ssorgatem commented on 2019-06-17 20:56 (UTC)
@alexzk it behaves like upstream, which is, by default, it copies the DXVK libraries to your prefix, which means they are not automatically updated when you update the package.
If you want that, use the "--symlink" argument.
Namarrgon commented on 2019-06-15 16:58 (UTC)
$pkgdir needs to be quoted properly or the build will fail in directories that contain whitespace.
alexzk commented on 2019-06-10 21:45 (UTC)
Can you elaborate in pinned comment, if I must repeat 'setup_dxvk install' after package upgrade for each wineprefix i have, or it implies automatically. Because early 0.xx versions were doing copies of itself = need repeat.
grawity commented on 2019-05-25 21:31 (UTC)
The conflict with dxvk-bin<1.0-1
is redundant, as a package already cannot be co-installed with itself... however, it does cause trouble for AUR helpers which don't support versioned deps. It should probably be removed.
Pinned Comments
ssorgatem commented on 2018-03-27 06:47 (UTC) (edited on 2019-02-26 12:20 (UTC) by ssorgatem)
To enable DXVK in a wineprefix, do the following (with the WINEPREFIX variable properly set):
setup_dxvk install
In order to uninstall DXVK from a wineprefix:
setup_dxvk uninstall