-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
New Package: Soundux.Soundux version 0.2.7 #141520
Conversation
This PR should satisfy issue #58855 |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
manifests/s/Soundux/Soundux/0.2.7/Soundux.Soundux.installer.yaml
Outdated
Show resolved
Hide resolved
66389a0
to
463dc80
Compare
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Automatic Validation ended with: (Automated response - build 856.) |
Automatic Validation ended with:
|
Hi @og-mrk The installation is unattended, but installs a driver which isn't unattended: Unfortunately, installer switches are not usually provided for this situation. Are you aware of an installer switch to have the driver silently install as well? |
Hello @stephengillie Sadly after reading through the Original Issue requesting this package, I've noticed that the same problem is happening over here, that being The Driver Installer isn't Silently Installing when Soundux is installing, the only possible way to install programs like this one is by using Dependency Resolution, a Feature that's still not fully supported by Anyhow, my apologies for not checking before making this PR, hope I didn't waste much of Maintainer's time, thanks for the help as always, and have a nice day. Note: I'm still hopeful to making this package install completely unattended, so I'll convert this PR to Draft for time been. |
463dc80
to
fc89d1f
Compare
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Like I've stated before, I'll look into this PR when Soundux have implemented an installer that is separate from the Driver Installer. Which unfortunately, I don't really have a clear idea as to when this will happen. |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow