matchmycolor.ColibriBeta version 22.3.1.9988

[matchmycolor]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[matchmycolor]

@microsoft-github-policy-service agree [company="matchmycolor"]

[matchmycolor]

@microsoft-github-policy-service agree company="matchmycolor"

[stephengillie]

Hi @matchmycolor,

This package requires the .NET Desktop Runtime 6.0.5 (x86):

I tried using the package Microsoft.DotNet.DesktopRuntime.6, but it must be a 64-bit package, as the installer generated the error even with it installed.

[matchmycolor]

Yes, we have some prerequisite dependencies for .net runtimes. We also have an installer that includes these dependencies. Should we publish this installer with winget? What is the proper way of dealing with prerequisites?

[denelon]

We're working through support for dependencies. It's currently an experimental feature. The one open remaining item is updating the path for the install flow so the dependency is recognized by the "main" package to be installed.

• [Dependency Issue]: Dependency can't be found by main installer after it's installed winget-cli#2939

If you publish a version including dependencies, the PR can be approved.

The schema supports referencing dependencies, but the issue mentioned above is the blocker.