While looking for something else I ran across this dialog about Exodus at https://github.com/AppImage/AppImageKit/issues/963:
"
Calinou commented May 24, 2019
What about using Exodus? It should work well with command-line tools at least.
@anderspitman
Author
anderspitman commented May 24, 2019 •
Wow exodus is awesome! And very easy to use. I ran it on my samtools binary and it just worked. So it seems like the way to go would be to run exodus on a dynamically linked binary, then package the exodus bundle into an AppImage for easy distribution (and perhaps versioning)?
@Calinou
Calinou commented May 24, 2019 •
You could compress and distribute the binary generated by Exodus directly, but if you want better desktop integration, you'll want to pack it into an AppImage (which may or may not work, I haven't tested)." [Elsewhere, it was reported that it does work].
As 'Exodus' in the context of Linux was unknown to me I followed the path to https://github.com/intoli/exodus where it says:
Exodus is a tool that makes it easy to successfully relocate Linux ELF binaries from one system to another. This is useful in situations where you don't have root access on a machine or where a package simply isn't available for a given Linux distribution... With exodus, transferring a piece of software that's working on one computer to another is as simple as this.
exodus aria2c | ssh intoli.com
Exodus handles bundling all of the binary's dependencies, compiling a statically linked wrapper for the executable that invokes the relocated linker directly, and installing the bundle in ~/.exodus/ on the remote machine."
Well, this is all way above my pay-grade. But I figure some of our vanguard might not already know of its existence and might find it useful.
