🐧 Initial commit of bin-wrapper

[jonathonf]

This is an experimental hook-wrapper combo which allows for automatic wrapping of JuNest applications ready for use in the outer system's $PATH. It's essentially an extension of the Command Not Found fallback but allows users to explicitly use JuNest packages "natively".

Having this in place should also allow for future enhancements around application launchers (.desktop files), i.e. when the executable is in $PATH then you can use just Exec=executable

[fsquillace]

Hi,

Thanks for this pull request and sorry for being so late here! I find it very interesting though.

I am wondering how this would differ from https://github.com/fsquillace/junest#run-junest-installed-programs-directly-from-host-os ?

As of now, executable files under /usr/bin/ get the corresponding wrapper automatically created/deleted once exiting from a JuNest session. One thing I like about your PR though is that the wrapper management is handled separately via commands which maybe interesting when troubleshooting or, in general, managing such wrappers. I am wondering whether there are other benefits which I am not seeing here.

Thanks again!

[jonathonf]

The original reasoning was to automatically wrap the JuNest executable so it could be used directly within the host OS but I'll have to look again at this - things may have changed significantly over the past couple of years!