Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add WAU winget informations #736

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

FaserF
Copy link
Contributor

@FaserF FaserF commented Oct 14, 2024

Proposed Changes

As WAU is now installable with an MSI, it is now also officially winget compatible. I have submitted the package to Microsoft:
microsoft/winget-pkgs#182735

This PR adds informations on how to install WAU with winget and adds WAU to the default update exclusion list.

Related Issues

(Github link to related issues or pull requests)

README.md Outdated
winget install Romanitho.Winget-AutoUpdate
```

You can use [Winget-Install](https://github.com/Romanitho/Winget-Install) to deploy the package for example in Intune:
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The thing is, I will not maintain that repo anymore, as winget-install is part of WAU now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Am I wrong, but right now, not everything has been moved from winget-install to WAU, right?
"(Will be part of WAU - Work in progress)".

Therefore doesnt it make sense to start like this and then change the README again once everything has merged to WAU?

But of course, I can remove that part if you want to.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The script at Winget-Install.ps1 is part of WAU and is maintained here.

The main goal of this script is to install WAU and use it as a dependency for all your Winget packages. This way, you can create empty packages with the following command: "%systemroot%\sysnative\WindowsPowerShell\v1.0\powershell.exe" -ExecutionPolicy Bypass -File "C:\Program Files\Winget-AutoUpdate\Winget-Install.ps1" -AppIDs Adobe.Acrobat.Reader.64-bit

This way, Mods and stuff are also applied.

But i'm open to have a standalone repo with that. But double repo to maintain 😅

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks understood. Maybe you should then archive your old repo and make a link to WAU and the script there. For example I am using winget-install and WAU since your early days and I always thought that this is still WIP, havent noticed that Winget-install is already completly obsolete.

For me personally, those are two completely different things (WAU vs. winget-install) as we dont install apps with WAU, WAU is just for updating? But in the end it is how you want to handle your tools :) Have a look at the latest commit, I hope thats fine.

Until now my package at Microsoft hasnt been approved yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants