Arch Linux User Repository

I included an automatic checksum update simply because I assumed that having a checksum would be better.

I used the command "mv" instead of "install" because moving is instant.

In the end is up to you which of those ideas to implement. I don't aim to total agreement, but to the further as possible agreement. Just keep in mind that everything I do is for a reason.

The most important part I believe is that the package upgrades well by itself, without human attendance on normal conditions.

@es20490446e I don’t understand the automatic checksum update, why not simply uses SKIP as sha256sum?

I am going to fix missing files, but is the good practice should be to use the install command?

The current package has an important bug, it doesn't include the following folder: /usr/share/icons

When the emulator launches for first time it copies that folder into: ~/.config/rpcs3

If the folder is missing basically the emulator won't work, except if the user had that folder previously.

The following PKGBUILD fixes all the issues, plus it automates any future updates. Tested to work without errors.

Updates will be available instantly as soon as published upstream, without packager attendance. It will work even if the directory structure changes, and even bring new checksum from upstream.

Private functions and variables names are started with an uppercase letter, so they cannot conflict with the ones in makepkg.

https://bin.privacytools.io/?853352e72ee0c919#P42jcLMLyh7LAcbAD4UnNMudRwwePMnFb9FXutUzNIw=

I have also discovered that the package is missing some important files, triggering the following bug:

https://github.com/RPCS3/rpcs3/issues/6007

I will try to fix them.

I have enhanced this package PKGBUILD so it automatically updates on a new release.

This way you would no longer need to update the info manually. And the offered release will be warranted to be the latest, without the need to compile from Git.

https://bin.privacytools.io/?e1d3844620c0b510#mUp1MhvQZc/ZrzNHmYgIkhDPvOYgWRrA90KMSVzHNWw=

I just update the dependencies according to namcap recommendations.

Looks like you need glew2.0 instead of glew1.13 now

Hi,

New 0.5 version causing error

rpcs3: error while loading shared libraries: libGLEW.so.2.0: cannot open shared object file: No such file or directory

sudo find /usr -iname 'glew' -print

/usr/include/GL/glew.h

/usr/include/GL/wglew.h

/usr/share/licenses/glew

/usr/share/cmake-3.10/Modules/FindGLEW.cmake

/usr/share/cmake-3.10/Help/module/FindGLEW.rst

/usr/lib/pkgconfig/glew.pc

/usr/lib/libGLEW.so

/usr/lib/libGLEW.so.2.1.0

/usr/lib/libGLEW.so.2.1

/usr/lib/libGLEW.so.1.13

/usr/lib/libGLEW.so.1.13.0

/usr/lib/libGLEWmx.so.1.13.0

/usr/lib/libGLEWmx.so.1.13

/usr/bin/glewinfo

oh unfortunately, the new version causes me problems with my pad. So I switched to the previous version, and with that one it works perfectly. If anyone has problems with their gamepad with the new version, try to switch back to the version of 2017-12-02