It is absurd that an AppImage requires flatpak to install it.

[GreyGeek]

https://appimage.github.io/Bottles/
which leads to
https://github.com/bottlesdevs/Bottles/releases
which requires one to use Flatpak to download the AppImage of Bottles, or be forced to use the source code and compile the app.
Their claim:

AppImage is broken, we are investigating, please use Flatpak in the meantime.

[claydoh]

Don't get yer undies twisted

It is simple. Nowhere on the Bottles website are appimages even mentioned The appimageHub page is not necessarily created by the bottles team. There hasn't been an appimage release afaik since December, actually early January.
The bot that scraped the bottles github page for AppimageHub last ran in June.

Currently there is no appimage for the project, but it seems to be being worked on
https://github.com/bottlesdevs/Bottles/issues/1272

https://github.com/bottlesdevs/Bottl...Aopen+appimage

Specifically:

:Caffe (the default runner in Bottles) requires glibc 2.32 or higher

if you are on Neon (aka Ubuntu 20.04), you ain't got that version.

And technically, from Appimage's own guidelines, this too-high a glibc (I think) requirement precludes Bottles from even being listed on appimagehub anyway.

[GreyGeek]

Ya, I read all of that, and I read the thread where the guy supposedly developing the AppImage for Bottles complains about his problems.
When he finished this is what he had done. Pitiful.

The WHOLE purpose of AppImage is that the application lives inside the image and doesn't touch user space or files, which would make the glibc requirement moot. Keeping references inside his image is something he couldn't accomplish hence Flatpak. So sad, too bad.

[claydoh]

??

When he finished this is what he had done. Pitiful.

THAT is the build instruction for the appimage, or rather the work-in-progress for it.


I think we are reading two different things here.

[GreyGeek]

I know. He said he couldn't reliably build the AppImage. That's probably why.