-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retroarch home directory symlink #3894
Comments
Yes, that's true and the same it's true for any other program/emulator/port that's handled by RetroPie - after all, that's what is supposed to happen. The programs installed by RetroPie are not 'isolated', the scripts will just automate their installation.
Yes and this is why the removal has a big warning about keeping or saving the configurations, specifically for this cases.
The If you have any other support questions, please use the forum, as instructed in the issue template. |
How so? Each of these programs has own configuration stored in master...9p6:RetroPie-Setup:master Retroarch was a bit tricky to get because it has so many subdirectories but for other packages it should be a lot easier.
The expectation is that add-on software installed to
Sure the config folder can still link to retropie configurations without seizing default config locations.
This is not a support question |
The current retropie setup hijacks
~/.config/retroarch
directory from existing installation by symlinking it to/opt/retropie/configs/all/retroarch
. This makes it awkward to run an independent retroarch installation (installed from Debian repo, Ubuntu PPA, compiled from source...) because now two different versions share the same config dir. It can also lead to data loss during removal for anyone unaware of implications of this setup.What significance does the symlink have for retropie? Does it exist solely for convenience of someone running
/opt/retropie/emulators/retroarch/bin/retroarch
directly? Is it necessary to support it in such way?The text was updated successfully, but these errors were encountered: