https://salsa.debian.org/sgclark-guest/squashfuse

https://salsa.debian.org/sgclark-guest/libappimage

both in debian

libappimage is in and added to kio-extras for thumbnail goodness.

Now investigate adding other appimage bits
appimaged ?
appimageLauncher https://www.appimagehub.com/p/1228228 ?
and Discover in master has support for appimagehub.

The last bit exposes scary security issues we need to understand and decide on.

Discover doesn't export appimagehub without packaging and installing scratch/apol/xdgthing so we'll ignore it like Discover wants us to.

But we should install appimagelauncher by default. @scarlettmoore has said she can get that into Neon.

Discover should ask for it in cmake to be consistent.

Hi!
https://packaging.neon.kde.org/backports-bionic/libappimage.git
Is this a mirror of my repo?
https://salsa.debian.org/sgclark-guest/libappimage
I would like to just update my repos in debian salsa, though I guess I can just merge it in via remote add.
Where should I put appimagelauncher? neon-packaging or this bionic-backports thing? Can I mirror my repo?
Thanks,
Scarlett

It's a clone of your repo for libappimage yes, you should be able to add yours as a remote and merge in changes.

backports-bionic is normal when taking in repos from outside neon, you can make a new repo in backports-bionic and clone yours into it

appimagelauncher now in
the postinst script calls dpkg-architecture but that is part of dpkg-dev which may not be installed. If this is needed it needs a Pre-Depends

Also added to iso seeds and isos rebuilt then put on social media

This in fact only became active recently.