-
Notifications
You must be signed in to change notification settings - Fork 129
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
Appimage download #2991
Comments
We could look into providing AppImage downloads if there's demand. Until then, it's fairly easy to run Nicotine+ from git: https://github.com/nicotine-plus/nicotine-plus/blob/master/doc/TESTING.md#git Alternatively, download the source code here and run the |
I have no idea how I missed the part about it being written in Python... sorry about that 💀 But the bit about the GUI being GTK is something you may need an appimage for I personally don't have a system python, though I do have 7 python interpreters on my system in a portable location... While I do have my system packages for python and GTK, sadly extracting those to a local AppDir doesn't seem to give me something runnable... |
cx_Freeze (which we use to create our Windows and macOS packages) also added support for AppImage recently. I haven't looked into it yet, but reusing our existing setup script would be great. |
Given the closed source client is downloadable as an appimage, this FOSS client should compete with them rather than restrict users to various package managers only
It's not even easy to build an appimage myself from the package list because most listed repos don't provide binary downloads of their packages, and the ones that do provide binaries that are too new for my glibc
The closed source appimage was bult in 2018, so it'll run for me, but I would like to use a client I can trust
Appimages are very easy to build, just compile to a directory (
nicotine.AppDir/
), and write an AppRun:You may also need to provide a .DirIcon before the actual appimage may build
Additional context:
1: I don't use package managers because they've repeatedly proven to be broken and unreliable, every last one of them
2: I won't use a Linux kernel >= 6.0 because I don't agree with the Rust movements and forced additions (memory safety takes skill, and Rust is not a solution for that)
Currently the kernel I use is 5.15 from Artix with glibc 2.35
but I'm looking to switch to SliTaz 5 which is 3.16 allegedly
(older means less bloat (no additional nonsense), which may mean less exploits if the kernel is selected and other exploits patched with care)
The text was updated successfully, but these errors were encountered: