Gentoo packaging

[DocMAX]

Can you please add a Gentoo install option? (an ebuild)

[TheAssassin]

I have no clue about Gentoo packaging and I have no time to learn this. You should ask the Gentoo maintainers to package this application.

That said, if there are people willing to contribute some script to this repository, please send a PR.

[q-g-j]

I made a binary based ebuild some time ago. You may get it here: qgj-overlay Here is the link to the ebuild: appimagelauncher-bin-2.2.0.ebuild (needs systemd as the init system!)

Instructions for layman:

sudo layman -o https://raw.githubusercontent.com/q-g-j/qgj-overlay/master/qgj.xml -f -a qgj

add app-misc/appimagelauncher-bin to /etc/portage/package.accept_keywords/custom, then:

sudo emerge app-misc/appimagelauncher-bin

[10leej]

I made a binary based ebuild some time ago. You may get it here: qgj-overlay Here is the link to the ebuild: appimagelauncher-bin-2.2.0.ebuild (needs systemd as the init system!)

Instructions for layman:

sudo layman -o https://raw.githubusercontent.com/q-g-j/qgj-overlay/master/qgj.xml -f -a qgj

add app-misc/appimagelauncher-bin to /etc/portage/package.accept_keywords/custom, then:

sudo emerge app-misc/appimagelauncher-bin

That requires installing gentoo with systemd right? AT least thats what I'm seeing in the ebuild. Anyway to install it with open-rc or does appimage launcher need systemd to function? Not that I'm opposed, I'd rather just have one init system on my gentoo install and not two of them.

[q-g-j]

Sry for the late reply. Unfortunately, this ebuild is for systemd only. This is a binary package which depends on the systemd libs. I couldn't get appimagelauncher to compile on my gentoo system when I tried it once.

[TheAssassin]

Out of the box, AppImageLauncher depends on systemd, there have been no efforts to port it to other init systems. The main reason is the support for user-level daemons.

[adcdam]

even flatpak work without systemd

[TheAssassin]

So does AppImage? Please keep your whataboutism for yourself. You added nothing to this discussion.

[adcdam]

no i can launch whatever appimage i want without systemd. It s your program creation is not about whataboutism. It s a pity you made it this way. there are other inits outthere besides systemd.

[TheAssassin]

Your comments are off-topic nevertheless. First of all, this issue is about Gentoo packaging, something that needs to be done upstream anyway. Second, the fact that AppImageLauncher out of the box only supports systemd is because of time constraints. The vast majority of distros and thus users uses systemd, it works just fine, and it supports user-level daemons, something that no other init system does. Adding custom daemon functionality is a lot of work, most users wouldn't benefit from it either, and I simply do not have the time to work on this.

In any case, you made it sound like AppImageLauncher was necessary for AppImages to work, which is just wrong. This tool is just a helper that works with AppImages, but it is not a dependency of AppImages. Also, it is completely irrelevant how Flatpak works to either discussion. Flatpak is a completely different design, and they ship their own root-level daemons, something which neither AppImages nor AppImageLauncher require.

If you want to suggest support of other init systems (which is slightly misleading, it is more about adding some kind of integrated daemon management to appimagelauncherd), please open a new issue.

[adcdam]

In any case, you made it sound like AppImageLauncher was necessary for AppImages to work, which is just wrong. No, i didnt say that, i know how to launch a appimage: chmod +x appimage ./appimagename dont worry i will not bother with your program. Developers this days need to calm down, they read something that they dont like and they get furious, angry. best regards.