Open g0t4 opened 3 years ago
We've discussed this internally. In some cases, there are many installer nodes. I think we're leaning towards winget show foo --verbose
.
A better way to achieve this is via CMDLETs and using -WHATIF
I agree this would be a nice default feature so that winget can interact meaningfully with the source manifest. There are automations and filters that may require that information specified by the creator of the manifest (custom cli args). A workaround via Powershell:
(Invoke-WebRequest -URI "https://raw.githubusercontent.com/microsoft/winget-pkgs/master/manifests/a/Adobe/Acrobat/Reader/64-bit/21.007.20099/Adobe.Acrobat.Reader.64-bit.installer.yaml" -UseBasicParsing).Content
Description of the new feature/enhancement
When installing packages I like to review what will happen. Often in detail. Especially for first time packages.
http
links--instead ofhttps
--that could be a risk?Proposed technical implementation details (optional)
Homebrew has
brew cat
for this very task. Hence the suggestion ofwinget cat
Or, we already have
winget show
and it dumps much of the information, but not all of it (verbatim). So, another option would be to add awinget show --verbatim
flag or similar. In fact, this is where I first looked to see if the option already exists (hopefully I didn't miss it)!Right now, I can poke around on GitHub and infer what manifest is what. But I can easily make a mistake. It's potentially time consuming. I could look at the wrong version. And I'd prefer to stay in the CLI flow quite often and not need a browser too.
I have some companion requests for similar commands to provide additional information about a package, I'll open separate requests for those so as not to put too much in here.