Skip to content

Conversation

ridgekuhn
Copy link

@ridgekuhn ridgekuhn commented Oct 29, 2021

Hello,

I've written a cloud sync utility using rclone, systemd, inotifywait, and bash. It registers save directories for RetroArch (based on the user's retroarch.cfg) and allows the user to sync their saves with an rclone remote either manually or automatically in the background. It also includes support for a few ports, the standalone ppsspp emulator, and multiple builds of RetroArch (ie, if the user is on a 64-bit distro and has both 64-bit and 32-bit builds of RetroArch). I've tried to make it easy to extend, so more ports and standalones should be supported in the future. There is also a version for ArkOS.

Video here: https://youtu.be/-jmoS1xwVcI

I couldn't find any documentation on writing a RetroPie module, so I've taken my best guess and would appreciate feedback on this if it seems like a good candidate to be merged in. Any issues with the app itself should go to the project repo.

The only issue I've encountered so far is that the RetroArch build included with the 4.7.1 Raspberry Pi 2/3 image does not respect the sort_savefiles_by_content_enable and sort_savestates_by_content_enable settings in retroarch.cfg. (Building from source or downloading the updated binary works as expected.) Is there any way to get the packages script to update RetroArch while installing this module?

Thanks!

@joolswills
Copy link
Member

Sorry but I don't want to include this into core RetroPie but you can include it as an external module via the ext/ folder and provide users with instructions to install etc.

@ridgekuhn
Copy link
Author

Understood. I would appreciate your negative feedback if you have any.

@joolswills
Copy link
Member

Well - if we included something like this, I would prefer it to be part of RetroPie-Setup than we maintain rather than an external project. But you can provide instructions for users to install it and use it as needed as an external scriptmodule.

@ridgekuhn
Copy link
Author

ridgekuhn commented Dec 5, 2021 via email

@joolswills
Copy link
Member

joolswills commented Dec 6, 2021

I think it's something I would consider, although right now I'm looking at bugfixing and working on existing PRs before our next image. But it's definitely useful.

All installed ports should be in /opt/retropie/ports and the folder name will be the script module ID. However I intend to add to the admin modules so you can query the script module meta data from the command line (no ETA, but I have a use for it myself)

Regarding the ext folder. It expects repositories to be checked out there that have the same structure as RetroPie-Setup. Eg ext/YOUR_REPO that contains scriptmodules/supplementary/YOUR_MODULE.sh

There's no facility to update from RetroPie-Setup, or manage external repositories (yet) , but it should handle modules there and list them separately after our modules in the Manage Packages sections. And it will handle installing/uninstalling of external modules.

@ridgekuhn
Copy link
Author

ridgekuhn commented Dec 6, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants