Skip to content
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

Too many conflicts with regular Dolphin #103

Open
SuperSamus opened this issue May 19, 2022 · 1 comment
Open

Too many conflicts with regular Dolphin #103

SuperSamus opened this issue May 19, 2022 · 1 comment

Comments

@SuperSamus
Copy link

There are many reasons for a user to install both regular Dolphin and Primehack, but the two projects share many paths and names, which creates conflict that shouldn't be there.
For example, the settings path is the same, which something that a user probably doesn't want since Primehack has some exclusive settings.
Or worse, Linux package managers usually install applications globally, and there are many common elements that prevent both applications to be installed: the executable names are the same, the .desktop file is the same, the icons' names are the same...
On the AUR, there is a discussion on dirty ways to install both, and it would be better if there was no need to.

@SirMangler
Copy link
Collaborator

As a 'work around', if you avoid the optional make install step, you can simply add a portable.txt file next to the dolphin/primehack binary, and it will run in portable mode with all settings from within that folder, without PrimeHack installing itself to Dolphin's default locations or producing a .desktop file. You can then make your own .desktop file should you wish.

https://github.com/dolphin-emu/dolphin/wiki/Building-for-Linux#portable-build

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

No branches or pull requests

2 participants