TODO: Use CPack to create MSI output instead of NSIS. Same directory and application name, e.g.Manifest are located at winget-pkgs/manifests at master That could be a problem as the SWI-Prolog install file is considered malicious by some scanners. Join the Windows Package Manager Insiders Program ( ref)Īn automated process will validate your manifest file and check to make sure the package is not known to be malicious. Winget-pkgs ( GitHub) - Contains the manifest files for the Windows Package Manager Winget-cli ( GitHub) - The source code for the Windows Package Manager Client (aka winget.exe). Windows Package Manager AKA Winget ( Wikipedia) List of software package management systems ( Wikipedia) Microsoft makes no warranties, express or implied, with respect to the information provided here. Windows Package Manager and the winget tool are in public preview and may be substantially modified before they are generally available. I do recall that Keivan Beigi publicly posted his own personal account of the whole ordeal but I can’t find it this seems to be a news story based on that posting.ĭo not take this to mean I am opposed to Microsoft, just passing the story along.įound the personal account by Keivan Beigi. ![]() ![]() ![]() Windows 10: Microsoft now credits maker of package manager it ‘copied’ – but offers no apology I could see that taking me a week or more.įor Macs I can only be a bystander as I don’t have a Mac.Īs noted in the original post, the goal is to not only install SWI-Prolog but install SWI-Prolog with some packages and also install VSCode with the extensions and specifically VSC-Prolog. I don’t plan to explore modifying the build instructions for SWI-Prolog to possibly make an MSI file. I don’t mind taking the time to see what winget can do for Windows.
0 Comments
Leave a Reply. |