-
Notifications
You must be signed in to change notification settings - Fork 17
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 #60
Flatpak #60
Conversation
The previous setup was using a fixed commit, adding patches as required. New setup builds the ci branch, assuming patches are already applied.
Closes: #59 Also: Use proper LD_LIBRARY_PATH for oeserverd so it finds libraries
BTW: While you are on it: Could you update the beta branch with the new build when it becomes available? |
Alec... |
Thanks for merge & close! Just FYI: Both my PRs (also this) have been rebased on the ci branch. Unfortunately, this is how it looks when making a standard github PR. The alternative would be to just attach one or more patch files. Would this be better? |
Alec... |
1 similar comment
Alec... |
One commit on top the ci branch, aimed to fix #59
Closes: #59