Open ghost opened 3 years ago
To understand correctly: You create a Wine prefix outside of Phoenicis and then import it?
No. I mean that it works more like Q4Wine. So that every executable will be displayed in Phoenicis instead of only one executable. It works like this:
I don't see the use case for this. There's a whole bunch of applications in the container which you certainly don't want to run.
What if I have many executables in one container? I mean for example,if a game has 20 executables in it,then I would need to add them all manually to phoenicis. And yes,there are some little games that their gimmick is that they have many executables. And also,https://github.com/PhoenicisOrg/phoenicis/issues/2326 would be better,cause then if you want to run one executable inside a prefix,then you can just right click and open it with phoenicis,without this feature request it would be more confusing cause you have to think "did I already add this program to phoenicis or do I have to add it?".
In this case, I would strongly suggest to use a script which sets up the prefix and the shortcuts for all required executables. Doing this manually will just be a pain.
But it would be cooler to do this directly in phoenicis instead of using a script.
I don't see why a script which can be reused by everybody shouldn't be cooler than doing this manually.
What do you mean that the script does? I mean do you mean a bash script that adds a specific prefix to phoenicis?
I'm talking about the installation scripts: https://github.com/PhoenicisOrg/scripts.
But then I would have to do a install script for many programs,and that needs more time.
Only once and everybody else can use the script as well.
What I mean is,that you can add prefixes like how you can do it with q4wine. So that you can add the prefix,select which wine version it uses etc. But whats better with adding whole prefixes instead of one executable is,that then you can run every executable directly instead of one.