libstatgrab port

[Michael-Becerra]

• Changes comply with the maintainer guide.
• The packaged project shows strong association with the chosen port name. Check this box if at least one of the following criteria is met:
  • The project is in Repology: https://repology.org/project/libstatgrab/versions
  • The project is amongst the first web search results for "libstatgrab" or "libstatgrab C++". Include a screenshot of the search engine results in the PR.
  • The port name follows the 'GitHubOrg-GitHubRepo' form or equivalent Owner-Project form.
• Optional dependencies of the build are all controlled by the port. A dependency is controlled if it is declared an unconditional dependency in vcpkg.json, or explicitly disabled through patches or build system arguments such as CMAKE_DISABLE_FIND_PACKAGE_Xxx or VCPKG_LOCK_FIND_PACKAGE
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is brief and accurate. See adding-usage for context. Don't add a usage file if the automatically generated usage is correct.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Exactly one version is added in each modified versions file.

[vicroms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[vicroms]

I see a bunch of patches to the product code. Have you tried pushing these patches upstream? Although simple, there are many and they add up; if possible, we want the port to remain as close to upstream as possible.

[vicroms]

Have you tried pushing this patch to upstream?

[Michael-Becerra]

i have not attempted to push these up I will see if i can push these upstream.