You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: