Add Diskuv.OCaml.1.0.0.0

[jonahbeckford]

• 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.1 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).

[ghost]

Hello @jonahbeckford,
The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @jonahbeckford,
During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect then the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[ItzLevvie]

@wingetbot run

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @jonahbeckford,
The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.0 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode (https://code.visualstudio.com/) to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator Preview.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[jonahbeckford]

Hmm ... it does work for me in the Windows Sandbox using winget:

>> # Rerun the installer; if you are prompted for security now you'll be able to click through it
>> winget install --manifest ..\SandboxTest\manifest
>>
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer SmartScreenEnabled=Off
HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer SmartScreenEnabled=Off
Found Diskuv OCaml [Diskuv.OCaml] Version 1.0.0.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Starting package install...
Successfully installed
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs>

So am rerunning with updated .yaml to see if something I edited is making it pass for me locally.

It has things I don't like:

1. It takes ~2 hours to complete. That won't reduce until OCaml (the programming language) stops requiring the installation path to be embedded in its binaries. And that won't change for ~1 year.
2. winget does not install the dependencies Visual Studio Build Tools and Git. Nothing I place in Dependencies: seems to matter. It is not terrible since my installer will not install Visual Studio Build Tools and Git if they are already present and compatible, but I'm hoping to model these dependencies correctly.

And the wingetcreate is using ManifestVersion: 1.2.0 which is too new. I'll downgrade and resubmit.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @jonahbeckford,
During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect then the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[jonahbeckford]

This looks like a 2hr time limit since this succeeds in Windows Sandbox. I can withdraw this PR and resubmit when it is under 2hr if it is just the time limit blocking this.

(Some time can be shaved off if I didn't need to install Visual Studio Build Tools and Git when they are not already present.)

[denelon]

@jonahbeckford the long install time is causing us to time out. The client does have an experimental feature for dependencies, but we would still need to install those for validation. We're looking into options to see if there is something we might be able to do for packages that take an exceptionally long time.

[jonahbeckford]

No worries. Thanks for looking. I'll withdraw this PR and resubmit when the install time is shrunk. That will be a win for everyone concerned.