Release as a snap
exa seems like a really great candidate for packaging and publishing as a snap package: https://snapcraft.io/
Combined with https://build.snapcraft.io/, it provides a really easy way of publishing a binary package that is installable and useable in a bunch of places (including Debian and Ubuntu, which is what I particularly care about :grin:).
Just noticed #206 which is a pull request already addressing this. \o/
#206 is now merged, but the release is yet to be done.
@ogham do you need help with releasing this via snap?
It seems that the snap package is not available yet https://snapcraft.io/search?q=exa
Would be great to see this published to the snap store. Feel free to ping me if you'd like any assistance here! :)
bump
Bump. I'm running into the issue using Ubuntu 20.04 and exa not being available as a package, I don't like to jump through 20 hoops and compile it myself and then install it in a non package way (considering that it will be installed on many systems) and since I would assume that no package will be done for Ubuntu 20.04, snap is the logical choice. Is anybody working on this? This would really help exa become more wide spread, making it easy to install and use.
Bump! A snap would be great, because the vast majority of servers I am working with are still running Ubuntu 20.04. I would love to see this as a snap, because it would be one easy command to add it to every server I am working on.
Bump! Would greatly appreciate it if you could release on snap!
$ ldd $(which exa)
linux-vdso.so.1 (0x00007ffc90bde000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f42ad8fe000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f42ad8f4000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f42ad8d2000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f42ad78e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f42ad788000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f42ad5b3000)
/lib64/ld-linux-x86-64.so.2 (0x00007f42adca3000)
The exa binaries might not be statically linked, but I have never had any problems running it on various new and old systems on armv7l, aarch64 and x86_64, so I think you can treat as though it is.
Just put the files in these locations (I use GNU Stow to install it using symlinks from a git repository):
binary ='/usr/local/bin' man files ='/usr/local/share/man/manN' bash completion file ='/usr/local/share/bash-completion/completions'