-
Notifications
You must be signed in to change notification settings - Fork 1
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
PlayOnLinux AppImage #2
Comments
When you have faith, everything is possible. |
Actually, I am also not that interested in games but more in applications. Keep up your great work. |
Thanks |
Looking at this issue again, PlayOnLinux already distributes standalone versions now: Then for one AppImage we would need to just pack it, but the new issue would be to change the PlayOnLinux code to support wine-AppImage too. |
Maybe an AppImage build could even be added to https://github.com/PhoenicisOrg/phoenicis-winebuild? Would you be available to help? |
In fact I would like to do just that, but adding one extra patch to fix the username (Wine always change the Windows username getting it from the linux user that call it), so that I can use the wine bottle more easily on portable versions of LogosBible. I'm just waiting for them to finish this pull request: PhoenicisOrg/phoenicis-winebuild#126 |
Hi, I have merged the merge request PhoenicisOrg/phoenicis-winebuild#126 Feel fee to ask if you need any support to extend phoenicis-winebuild |
Thanks. Then I will start to play with the code :) |
Hi @qparis are you familiar with the concept of AppImage? What do you think, would you be interested in adding an AppImage build to phoenicis-winebuild? There are already several WINE AppImage builds out there, but having an official PlayOnLinux AppImage build would no doubt be beneficial. Existing WINE AppImage projects include:
Let me know if you have any AppImage-related questions, I know it pretty intimately ;-) |
Hi! Indeed it would be interesting to support several packagers. Phoenicis wine build could automatically build any version to an app image format. What do we need to know to create a wine app image from a source root? Concerning POL itself, we already support flatpack in our latest version so I see no reason why we could not support app image. |
That's good! My project: The script that run the AppImage is the main thing: So now we have AppImages (like https://github.com/ferion11/Wine_Appimage/releases) that can run wine32 on no-multilib linux distributions and installation. Using the same technique I made one PCSX2 (that only have 32bits and need multilib) AppImage that can run on pure 64bit, no-multilib, linux distributions (having only around 150MB): https://github.com/ferion11/PCSX2_Appimage/releases |
Also see my notes at https://github.com/probonopd/libhookexecv, and my proof-of-concept at https://github.com/probonopd/libhookexecv/releases/tag/continuous - e.g., the https://github.com/probonopd/libhookexecv/releases/download/continuous/NotepadPlusPlus-7.7.1-x86_64.AppImage which contains both the application and WINE fully self-contained so that it will run on a 64-bit Linux system without multilib... in an AppImage that is just 27.4 MB |
@qparis great to hear! 👍 I am happy to support the effort in any possible way.
Shall we discuss this here or would you prefer to discuss that in a ticket over at https://github.com/PhoenicisOrg/phoenicis? |
Depends on what you want to do:
Feel free to open a ticket :) |
Do you think you could make a PlayOnLinux AppImage, including WINE? I am sure it would be appreciated by many users.
The text was updated successfully, but these errors were encountered: