Add support for frugal distros packages

[CoalaVerde]

Problem

https://forum.porteus.org/viewtopic.php?f=48&t=11766
Might be a good idea to add support for those packages and leverage soar as some sort of interoperability layer between such distros. The thing is those packages CAN be used outside of them in any other distro, thus I think it would be a good addition to it, since they're sort of universal (even though just a small niche group uses them)

Expected behavior

You should probably change your Feature Request issue templates...
These questions just don't make sense to me outside of a normal Bug issue

[QaidVoid]

Started working on this. Extraction side is done: .sfs/.xzm/.sb via squashfs and .pet too. Packages install into their own directory, commands get linked, desktop entries and icons register, uninstall is clean. Tested a few from the Puppy/Porteus repos and plain CLI stuff works.

GUI apps are the problem, and that's what I want to ask about. These modules are a slice of the parent distro's filesystem. On the parent distro they work because the module gets union-mounted over a matching base at boot, so anything they don't bundle comes from the base. Outside of it, an app runs only if the host's libraries happen to match, and mostly they don't.

So how are these apps supposed to work? Is the expectation that the module bundles its runtime deps (the ones that do, run anywhere), or is providing the parent-distro runtime in scope for soar, e.g. extracting the tree and running it against a fetched base of the matching distro in a sandbox?