You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched all issues/PRs to ensure it has not already been reported or fixed.
I have verified that I am using the latest version of Scoop and corresponding bucket.
Package Name
mpv
Expected/Current Behaviour
I noticed that on the latest version of mpv 0.35.0 the mpv command stop working under gitbash.
This was confusing because the exact same version was installed on another PC and the command is working in gitbash without workarounds (alias or script file to map mpv.com). The cause for this issue was the change from shimming to use the path to mpv.
From the PR I see that's something related to mpv.net which I'm not very familiar with. Is this change required for the simple mpv? Because without the shim gitbash won't recognize mpv.
There are workarounds as I've mentioned before like aliasing mpv to mpv.com or simply creating a shell scrip to map to mpv.com but I'd like to know if this change if required for mpv in the first place.
Steps to Reproduce
On latest version of scoop install mpv
scoop install mpv
Open a bash shell (gitbash) and type mpv.
Observe that the mpv command is not recognized as a valid command.
You can verify that previous version using the shim does work by installing mpv using the previous manifest.
Install mpv with manifest that creates a shim (one commit before the change).
Using the binary with extension works (in my case I need to use mpv.com instead of mpv.exe or it will just open the player ui instead of outputing information), I know and that solution is fine for simple use cases but it doesn't work when mpv is expected on scripts.
The reason I found this issue is because it stopped working on ani-cli and I found an issue opened regarding that pystardust/ani-cli#959.
That's why I wanted to ask if the change made to use a path instead of a shim is required for mpv as the PR that makes the change stated that the issue is for mpv.net.
In any case if this change is going to stay, I'd like to add a better solution for anyone finding this issue.
Create a file in directory that it is in your path (E.g. $HOME/.local/bin) and named it mpv.sh.
Open it with a text editor and add the following lines
#!/usr/bin/env bash
mpv.com "$@"
Add executable permissions to the file. E.g.
chmod +x "$HOME/.local/bin/mpv.sh"
That should map the binary (mpv.com in my case) to a script that gitbash can find. That way there is no need to add the extension and modify scripts of binaries that expect mpv (without extensions).
That's why I wanted to ask if the change made to use a path instead of a shim is required for mpv as the PR that makes the change stated that the issue is for mpv.net.
the current situation is more in line with expectations either itself or Windows, IMO.
You can also do it with scoop-shim(scoop help shim).
Prerequisites
Package Name
mpv
Expected/Current Behaviour
I noticed that on the latest version of mpv 0.35.0 the
mpv
command stop working under gitbash.This was confusing because the exact same version was installed on another PC and the command is working in gitbash without workarounds (alias or script file to map mpv.com). The cause for this issue was the change from shimming to use the path to mpv.
#9662
From the PR I see that's something related to mpv.net which I'm not very familiar with. Is this change required for the simple mpv? Because without the shim gitbash won't recognize mpv.
There are workarounds as I've mentioned before like aliasing mpv to mpv.com or simply creating a shell scrip to map to mpv.com but I'd like to know if this change if required for mpv in the first place.
Steps to Reproduce
mpv
.You can verify that previous version using the shim does work by installing mpv using the previous manifest.
mpv
command and observe the output that it recognizes mpv.Possible Solution
Scoop and Buckets Version
** Will update once I have the affected computer back **
Scoop Config
** Will update once I have the affected computer back **
PowerShell Version
** Will update once I have the affected computer back **
Additional Softwares
Git bash for Windows
Windows Terminal
The text was updated successfully, but these errors were encountered: