-
Notifications
You must be signed in to change notification settings - Fork 100
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
The creating of normal binary releases to avoid third-party developer bugs #1327
Comments
Last repository version (not a Flatpak) doesn't find dictionaries too... The last repository version finds all dictionaries. But it crushes (without any error on console output) in attempt to open any article and doesn't support the ZIM dictionaries. |
What is the the exact version ? |
The Flatpak version, that I launched now again, in Discover is as 23.12.23 and in "About the program" is as 23.12.07.b0086d5 at 2023-12-23T04:18:13. It crushed right now in mentioned manner and had the empty history journal... |
The problem with crush was solved, but with paths in Flatpak - didn't. |
The problem with paths in Flatpak was solved. |
Creating such binary requires dealing with differences between different distros and their different versions. It is a time sucking black hole that never ends. Feel free to try to restore the AppImage build, deleted code is here goldendict-ng/.github/workflows/ubuntu-6.2.yml Lines 87 to 102 in ffce71d
|
Describe the bug
GD-ng doesn't support any dictionaries path on partition containing Root ("/") even if there is only a symbolic link to folder on another partition. So, in case (of course, unusual) of only one partition using there will not be able to add any dictionary in GD-ng at all. This issue was labelled as "Flatpak", nevertheless Flatpak itself supports paths on partition containing Root, because GD-ng runs from it...
To Reproduce
Steps to reproduce the behaviour(the form lacks the letter "u"):
see link above.
Expected behaviour(--//--)
The compiling of usual binaries with statically linked libraries (for releases only and links to them in releases only, not how is now to Flatpak release in every pre-release). It avoids the need of root privileges for users too.
You may consult with huge number of developers here about how to make it (for example, with author of this binaries: it will be easy for You to find a common language with him, I think; but to make more simple binaries, like this)
OS and software versions
Additional context
Thanks in advance
The text was updated successfully, but these errors were encountered: