probonopd
appimaged: AppImages created using uruntime with dwarfs do not work.
The uruntime to create AppImages has an option to use dwarfs archives instead of squashfs. As appimaged directly reads the squashfs archive it makes it's integrations not work on them. We can probably add a work around, but since the type 2 spec is to use squashfs, should we add in a workaround for AppImages that are saying they are a type 2 AppImage, but are not adhering to the type 2 specifications? Issue on uruntime.
Well. Is there even a dwarfs filesystem for golang that we could use?
No, there is no go library for dwarfs, we'd have to rely on commands.
Well. Is there even a dwarfs filesystem for golang that we could use?
I could make some bindings, I've been wanting to convert the AppBundle runtime into one that doesn't have binary dependencies, at least to test how it goes and see if that improves anything. As I will still most likely keep using binaries, for ease of development & use.
Do tell me guys if y'all would be interersted in having dwarfs bindings using CGO
Well, so far the draft of the AppImageSpec does not specify any particular filesystem format for type-2 AppImages, but the plan has been since a while to standardize on squashfs with zstandard compression:
- https://github.com/AppImage/AppImageSpec/issues/34
However, due to the impressive results of dwarfs there has also been a consideration to standardize on it instead:
- https://github.com/AppImage/AppImageSpec/issues/36
As of now, no decision has been made. So squashfs with zstandard compression is currently the de facto standard.