id summary reporter owner description type status priority milestone component version resolution keywords cc blockedby blocking branch_state votes 3740 mc-wrapper.sh script is not installed in target bin directory sorin "While I am not sure if that's by design but here is the use case: as an user I want to be able to install and use mc and benefit from the ability to keep the current folder. This would usually be achieved by adding an alias `mc=mc-wrapper.sh`. This works well as long mc-wrapper.sh is in the PATH too. Now, the problem is that on MacOS the standard installation method is using `brew` which installs each package in its own unique (version based) target location and in the end it does symlink executables inside `/usr/local/bin`. Symlinks for mc, mcedit and mcview are created successfully without having to do anything. They also work very well. Here is an example: {{{ ls -l /usr/local/bin/mc* lrwxr-xr-x 1 ssbarnea staff 42 7 Dec 09:16 /usr/local/bin/mc -> ../Cellar/midnight-commander/4.8.18/bin/mc lrwxr-xr-x 1 ssbarnea staff 46 7 Dec 09:16 /usr/local/bin/mcdiff -> ../Cellar/midnight-commander/4.8.18/bin/mcdiff lrwxr-xr-x 1 ssbarnea staff 46 7 Dec 09:16 /usr/local/bin/mcedit -> ../Cellar/midnight-commander/4.8.18/bin/mcedit lrwxr-xr-x 1 ssbarnea staff 46 7 Dec 09:16 /usr/local/bin/mcview -> ../Cellar/midnight-commander/4.8.18/bin/mcview }}} As you can see this does not cover mcwrapper.sh which now is located inside /usr/local/Cellar/midnight-commander/4.8.18/libexec/mc/mc-wrapper.sh Yep, I could manually create a symlink to this location but this means that the next upgrade will break it. I am looking for a better alternative that would not break on upgrades, maybe even an option to install and activate the wrappers by default, if possible. If this would be possible it would be a great addition not only for MacOS but for all platforms. " defect closed major mc-core master wontfix no branch