[copypp] New port #35309

[i-curve]

• Changes comply with the maintainer guide
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
• 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 accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[i-curve]

@microsoft-github-policy-service agree

[dg0yt]

LGTM. But somebody else must approve.

[i-curve]

@dg0yt thanks for your suggestion.

[i-curve]

@dg0yt Hi, after I change the port file and commit it, git-tree need to change in the version's file. What's the mean git-tree? Am I doing the right thing by git's commit twice?

[dg0yt]

You are doing it right.
git-tree is an interal git thing refering to the (per-port-dir) filesystem state. You could update the commit message and even other directories (such as updating the records in versions/) without changing the git-tree reference, while the commit SHA changes everytime.
And it makes it possible to squash-merge PRs here.

It is just annoying, in particular with PR suggestions, that updating versions/ isn't automated.

[Adela0814]

Usage test pass on x64-windows and x64-windows-static.