microsoft-coreutils@2026.5.29: Adding Scripts, Remake shims#8110
microsoft-coreutils@2026.5.29: Adding Scripts, Remake shims#8110SiriosDev wants to merge 6 commits into
Conversation
| "cmd/arch.cmd", | ||
| "arch" |
There was a problem hiding this comment.
This doesn't seem to work.
> arch
MZ�$�
'MZ�$�' is not recognized as an internal or external command,
operable program or batch file.
> D:\Scoop\shims\arch.cmd
MZ�$�
'MZ�$�' is not recognized as an internal or external command,
operable program or batch file.
I'd suggest waiting for the next portable release. See: microsoft/coreutils#18
There was a problem hiding this comment.
Try rerunning PowerShell or opening another instance directly, otherwise the new $PROFILE is not loaded
There was a problem hiding this comment.
If it can only be used in PowerShell, then there's no need to create a shim.
I'd suggest waiting for the next portable release. See: microsoft/coreutils#18
There was a problem hiding this comment.
If it can only be used in PowerShell, then there's no need to create a shim.
As far as I understand, only pwsh requires these specific tweaks; cmd shouldn't, assuming I've got it right:
https://github.com/microsoft/coreutils#windows-caveats
There was a problem hiding this comment.
Isn't it confusing to create a shim that doesn't actually work? I think there might be a misunderstanding regarding how Scoop shims work. Please refer to:
-
https://github.com/ScoopInstaller/Scoop/wiki/App-Manifests#optional-properties
You can also create an alias shim which uses a different name to the real executable and (optionally) passes arguments to the executable. Instead of just using a string for the executable, use e.g: [ "program.exe", "alias", "--arguments" ]. See busybox for an example.
-
uutils: add symlinks for various tools #3482
[ "coreutils.exe", "arch", "arch" ]
For example, creating an
archshim creates an alias forcoreutils.exe arch.
There was a problem hiding this comment.
oh right, now should work
I thought about shimming the cmd files to follow the script's instructions, but it turns out that's not necessary because the script references the executables directly in the cmd subfolder
Following the raw script included in the original repository, I created a script that creates hard links in
binandcmd, removes the placeholder file, and modifies and runspwsh-install.ps1to referenceHKCUinstead ofHKLM, so thatUACis no longer required even forCurrentUsermode. (And Uninstall too of course).In this way, the shipped “patch” should apply to all
$PROFILE, except for legacy versions (>5.0), which are not supported by the original installerRelates to #8107
<manifest-name[@version]|chore>: <general summary of the pull request>