It may be useful in some cases to have binary registered globaly for associated binary shim to be available outside of the project directory.
When a global binary shim is invoked, it should temporarly activate the project where it's defined and run the command as usual.
It should also be possible to register any executable file as a global binary, so it's automatically registered in global path when activating the module for the first time. There should be a way to unregister all those global binaries too, either per project or system-wide.
It may be useful in some cases to have binary registered globaly for associated binary shim to be available outside of the project directory.
When a global binary shim is invoked, it should temporarly activate the project where it's defined and run the command as usual.
It should also be possible to register any executable file as a global binary, so it's automatically registered in global path when activating the module for the first time. There should be a way to unregister all those global binaries too, either per project or system-wide.