Skip to content
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

How to install ? #38

Open
thunderpants opened this issue Apr 21, 2023 · 12 comments
Open

How to install ? #38

thunderpants opened this issue Apr 21, 2023 · 12 comments

Comments

@thunderpants
Copy link

thunderpants commented Apr 21, 2023

Noob question.

Why not just upload a deb file or give us a build that doesn't require this Nix thing.

@Elinvention
Copy link
Owner

Thanks for your question. You are right, the README assumes that one is familiar with running python applications. You don't need a deb package or nix.
You can clone this repo if you know how to do that with git or download the source code and unzip it. Then double click efiboots (make it executable before if it isn't already).

@KaKi87
Copy link

KaKi87 commented Oct 29, 2023

Hi,
Would you consider making builds ?
Thanks

@Elinvention
Copy link
Owner

What do you mean by builds? Deb packages?

@KaKi87
Copy link

KaKi87 commented Oct 30, 2023

Flatpak, DEB, PPA, AppImage, or a binary of any form, would be nice, yes please.

@codefaux
Copy link

Here to ask for the same. AppImage would be best, runs on Any Linux, just download and chmod +x.

@KaKi87
Copy link

KaKi87 commented Jan 10, 2025

AppImage would be best, runs on Any Linux, just download and chmod +x

Flatpak would be best then, because you get automated updates in addition to the ability to run on any Linux.

Thanks

@codefaux
Copy link

codefaux commented Jan 10, 2025

AppImage would be best, runs on Any Linux, just download and chmod +x

Flatpak would be best then, because you get automated updates in addition to the ability to run on any Linux.

Thanks

This expresses a distinct misunderstanding with how AppImage works.

AppImage = download one file, chmod +x, execute, running app.

flatpak = install flatpak management/container/downloader service, download application container + all application container dependencies, assemble and launch, with permissions, restrictions, inaccessible folders and devices, manual mappings, etc etc etc

Appimage = ANY LINUX
Flatpak = One of 41 selected Linuxen, after installation of Flatpak management services

AppImage would be best, runs on Any Linux, just downlaod and chmod +x.

EDIT: 41 Linuxen claim; https://flatpak.org/ and https://flatpak.org/setup/ -- specifically not Any Linux

@KaKi87
Copy link

KaKi87 commented Jan 10, 2025

This expresses a distinct misunderstanding with how AppImage works.

AppImage = download one file, chmod +x, execute, running app.

Lol, tell me something I don't know.

flatpak = install flatpak management/container/downloader service, download application container + all application container dependencies, assemble and launch, with permissions, restrictions, inaccessible folders and devices, manual mappings, etc etc etc

That's plain bad faith.

I'm trying to tell you : Flatpak provides automated updates.

As in : you don't need to re-download an AppImage every time there's an update.

41 Linuxen claim; https://flatpak.org/ and https://flatpak.org/setup/ -- specifically not Any Linux

If your distro isn't among those, then you're not a normal user anyway, so you can compile a program from sources.

This issue is for normal users, who use easy distros. Distros that are supported by Flatpak.

@codefaux
Copy link

codefaux commented Jan 10, 2025

tell me something I don't know. (And some other bullshit stripped for brevity)

Bro your argument was any Linux and that was patently false in every way. Don't be a child. I'm not arguing with children on GitHub. Let's keep on topic here. Yeah flatpak and its massive orchestration service architecture handles updates. Congrats. That's not what I said, and it's separate from what you claimed.

Yes, you have to update appimage yourself. (Unless you use an appimage launcher which handles autoupdates too, without an orchesteation service.)

Flatpak runs on fewer systems, with more overhead for the user, the user's hardware, the developer, and the internet in general. It comes from a centralized repo, and depends on all of the behind the scenes flatpak services and subsystems. It limits the access and reach of the binaries within it by default.

AppImage is one compiled binary provided by the developer from GitHub Releases or literally ant other file transfer medium, downloaded and executed by itself. It's an extra makefile step, not signing up with a flatpack repo and keeping that up to date.

There's no choice if you're looking for reaching Any User on Any Linux.

@KaKi87
Copy link

KaKi87 commented Jan 10, 2025

There's no choice if you're looking for reaching Any User on Any Linux.

But we're not.

We want builds and automated updates because we're normal users using easy distros that Flatpak does support.

We're not using an exotic distro that targets advanced users who wouldn't need builds because having that exotic distro implies they're comfortable with building apps themselves.

@codefaux
Copy link

codefaux commented Jan 10, 2025

But we're not.

Oh, fair enough. I got the impression otherwise by reading the messages here -- better tell the guy who said this because he gave the distinct impression otherwise. He seems confused, overall.

Flatpak, DEB, PPA, AppImage, or a binary of any form, would be nice, yes please

@KaKi87
Copy link

KaKi87 commented Jan 11, 2025

he gave the distinct impression otherwise

No. AppImage is one option among many others. I never said I included it because of being able to run on any Linux.

In fact, AppImage or another binary form are my least favourite options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants