-
-
Notifications
You must be signed in to change notification settings - Fork 439
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
[Linux] Flatpak preparations #515
Conversation
…to flatpak_config
…uncher into flatpak_config
…uncher into flatpak_config
…uncher into flatpak_config
Any Update here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should be:
- --socker=wayland
In flatpak/org.heroic.yml
Don't miss that
So far: Heroic opens and I can Login, but it get stuck on the listing games part. I'm not sure if in a flatpak container Heroic will be able to execute legendary, it seems that is the issue but I need to investigate more. |
Why not just compile legendary and bundle it with the application? |
It's against the rules of Flathub |
Really? Didn't know that and Heroic already bundles the legendary binary. |
Flathub does not allow the use of pip install during instalations. The use of a network connection is not allowed during build I already ask for some of my Apps. You have to include all the whole dependency tree in the manifest. It's a lot of fun for me (not) to figure out how to build Qt from source or to figure out, why a build system that I never heard of before is not working during a Fltpak build. Luckily for you, legendary depends only on requests, which is no problem to include in a Flatpak. More Luckily for you, there is already a person who has a legendary Flatpak, but without working wine yet. You should try to contact him. |
@flavioislima |
Yes, good idea. We have a post on flathub forum but no one answered there yet. |
@mirkobrombin @gasinvein Thanks :D |
I'll take a look at it this weekend. Do legendary logs work now? |
Yes, I can see the output on the log screen now. |
Nice 😎 |
Just an update: I've made some tests but legendary keep crashing. I'm trying to use legendary as flatpak to understand if it's a heroic problem or legendary one. |
That's weird. can you see any log of those crashes? |
I had some permission overrides from old tests. After cleaning up everything including the configuration files, I am no longer able to log in via Epic. Legendary logs says I'm logged in:
but Heroic keep ask for login. There are other files I should clean? I've also performed a full reset from Heroic. |
…uncher into flatpak_config
…uncher into flatpak_config
…uncher into flatpak_config
Flatpak builds to be, ideally, published to Flathub.