Open technician77 opened 6 years ago
I'm not familiar with either one of those. If the Windows pacman uses the same commands as the Arch linux one (e.g. pacman -Syu
to upgrade everything), then it might work already. Can you check? I don't have access to a Windows machine.
For nuget, it looks like it might be straightforward to implement. Can you check if running (async-shell-command "nuget update" nil nil)
works? You'll have to have nuget.exe
in your PATH.
Sorry for the the late answer. I had to migrate from cygwin to msys2 and well not all packages I used were available but I managed. Yes, your are right pacman does already work since the syntax IS the same. The only thing I had to do was (setq system-packages-usesudo nil)
Someone wrote an equivalent of use-package for system packages based on your package. Looking forward to test it.
The nuget output is:
No packages.config, project or solution file specified. Use the -self switch to update NuGet.exe.
If I (async-shell-command "nuget update -self" nil nil)
I get:
Es wird auf Updates von https://www.nuget.org/api/v2/ |erpr’t.
"NuGet.exe" 4.4.1 wird zurzeit ausgef”rt.
"NuGet.exe" ist aktuell.
The german special characters (äüöß) seem to be broken. But beside this cosmetic issue it looks quite good.
Are there any plans to support pacman on msys2 (windows) or nuget in the future?