RetroArch

Edit Package retroarch

RetroArch is a frontend for emulators, game engines and media players.

It enables you to run classic games on a wide range of computers and consoles through its slick graphical interface. Settings are also unified so configuration is done once and for all.

RetroArch has advanced features like shaders, netplay, rewinding, and more!

Refresh
Refresh
Source Files (show unmerged sources)
Filename Size Changed
_service 0000002073 2.02 KB
retroarch-1.18.0.tar.gz 0019881666 19 MB
retroarch.changes 0000123194 120 KB
retroarch.spec 0000004374 4.27 KB
retroarch_migrate_old_config.py 0000001789 1.75 KB
Latest Revision
buildservice-autocommit accepted request 1160933 from Yunhe Guo's avatar Yunhe Guo (guoyunhe) (revision 84)
baserev update by copy to link target
Comments 9

Karol Sławiński's avatar

Changes referred to 1.8.6 version


Yunhe Guo's avatar

Fixed. Sorry!


Karol Sławiński's avatar

source code from version 1.8.6



Yunhe Guo's avatar

Fixed. We use a tar_scm service to exclude non-OSS code. And each time need to remove git clone folder manually, otherwise the source won't be updated.


Karol Sławiński's avatar

the labels in the entire application are partially mixed, they do not match the functionality - not applicable to the English language


Martin Jungblut's avatar

@guoyunhe

I don't think the retroarch-config.patch file is required. Please correct me if I'm wrong.

Here's my rationale: I think it would be better for users to be able to download extra cores using RetroArch's built-in online updater, rather than hiding that feature and providing cores as multiple, sometimes outdated packages. Not all cores are available as packages right now, but they may be installed via the Online Updater, but only if the user is smart enough to re-enable it.

I think it would be better for us to drop the libretro* packages altogether, and ship a build of RetroArch that focuses on using the Online Updater. We already ship Steam, and people download games through Steam itself, so I don't think the idea of distributing cores via RetroArch's own solution to be a bad one.

I'm maintaining my own build here: https://build.opensuse.org/package/show/home:martinjungblut/retroarch But I'd love for this to be solved, rendering my package obsolete.

Any thoughts are greatly appreciated, Thanks in advance



Yunhe Guo's avatar

Checkout the latest build. I changed it back to upstream config, with a migration script to help existing users upgrade.

openSUSE Build Service is sponsored by