-
Notifications
You must be signed in to change notification settings - Fork 12
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
Flatpak #155
Comments
Interesting. Thanks for the work. Does launching the emulator not work because of some sandboxing? |
Yes. Flatpak is a Container Format that is Sandboxed and has a Permission System. You can read more about Flatpak in the official Documentation. You have normally only access to what's available in the Sandbox. To solve the Emulator Problem, you have basically 3 Options:
If you built and installed the Flatpak, you can run |
@mchlnix Any update on this? |
Sorry, just getting back into it a bit. So option 1 is too much work and option 3 also doesn't sound great. I'd have to hope that the emulator is associated with the file type, which isn't always the case and then hope that the commandline interface supports just chugging a file at it. Option 2 kind of defeats the purpose of the flatpack, so making a deb file for linux might make more sense then. Also the user would have to spawn the flatpack with In general it's a bit too much effort for me, although you've done a lot already. If you are passionate about having a flatpack version, then you can go ahead and make one yourself. It looks like you've already done the leg work anyway. So few people use the linux version, that I think most can probably just clone the repo and run it like that. |
Don't worry. It's always the case. I haven''t seen an NES Emulator which don't do that. If no Program is registered, the User will be prompted to choose a Program to open with. On KDE for example you will see the following dialog, if no Emulator is installed:
No need to hope.
It's the defeat's the purpose half. The App is no longer Sandboxed, but you can still install it on any Linux System.
A DEB file only works on Debian based Systems. A Flatpak works on any Linux System out there. You may also need to adjust the DEB file for different versions of Debian based Operating Systems.
No. That's the command you need to run inside the Flatpak. It works out of the box, as long as the Flatpak have the Permission.
It don't hurt to give Linux Users a better experience. You App will be promoted on Flathub, can be installed with one click on every Linux Distro out there and is guaranteed to always work. Users will also get Updates automatically. That all comes free of charge. |
I'll have another look, but I make no promises. While a deb file only works on debian distros, afaik that's most users' distros. Not sure how widespread flatpaks are already. I had heard of them before, but never used them. An appimage almost makes more sense to me. They can also be updated in place and you don't need to download anything specific to make it work, iirc. This is honestly something that could be contributed, if it's really wanted. |
They are very Widespread today. Flatpak is preinstalled o many Linux Distros (e.g. Linux Mint, SteamOS) today. You can install Software from Flathub directly in the Software Center out of the box. If it's not pre installed, you can easily install it. It also allows Users to discover Software in an easy way. Many Users have Flatpak set up, as it's in many cases the best way to get the newest Software. Flathub has millions of active users.
You can have both. A Flatpak provides better integration into the System and is safer, while a AppImage is a more portable way, which has a few problems. If you want to create an AppImage, you ca use my tool pyproject-appimage, which allows you to create AppImages of Python packages. The only thing you need to do is making SMB3-Foundry installable with pip. pyproject-appimage does the rest. |
Ah, interesting. I'll have a look. I've been questioning releasing the editor as one executable, instead of just the source with an executable running the python code for a while. I did that because workshop did it before (although even that isn't really true). |
I created a Flatpak for SMB3-Foundry. This allows publishing on Flathub and installing on any Linux Distro out there (this does not work with the Binary). You need these files:
io.github.mchlnix.SMB3-Foundry.yaml
python3-modules.yaml
Check out the Documentation how to build this. Some things needs to be done e.g. launching the NES Emulator is not working, but it is general working. Tell me, if you are interested,
The text was updated successfully, but these errors were encountered: