In the meantime, I believe that https://github.com/osquery/osquery-packaging/pull/20 will solve the only outstanding issue

We had all the files setup in osquery, we just needed that verification bit, and hopefully after that the pipelines will be finished for chocolatey

As for getting 5.1 and 5.2 up, hopefully I'll have it sorted this evening, I just need to patch in the verification file

So along these lines, here's another painful bit: Chocolatey requires us to specify an icon for the package. It notes explicitly to use

iconUrl

which is part of the (now deprecated) NuGet specifications here. However, they haven't updated to consider the

iconUrl

value as being deprecated. We can specify `icon`for cpack, which we do here, so when

cpack

generates our nupkg we get a valid package, however any manual attempts to create said package with chocolateys shitty tooling will result in a failed build, as it doesn't consider

icon

valid. This hopefully wont be an issue if Chocolatey ever decides to update their shit, they in theory will adopt the latest nuspec guidlines, but if they change they're moderation requirements before that we may start failing any attempts at automated submissions.

Another idea here would be to possibly look at other Windows package distribution lines, like vcpkg or something