[high-jump] New Port

[hanjingo]

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

[BillyONeal]

Please complete the new port checklist I uncommented in the PR description. In particular I think the name likely needs to be hanjingo-high-jump because high-jump is neither in repology, nor does that repo appear in the first page of search results for "high jump c++" for me.

[hanjingo]

Please complete the new port checklist I uncommented in the PR description. In particular I think the name likely needs to be hanjingo-high-jump because high-jump is neither in repology, nor does that repo appear in the first page of search results for "high jump c++" for me.

Thank you for your suggestion. I checked on https://repology.org/ and did not find any existing project named "high-jump". Therefore, I would prefer to keep the current port name "high-jump".

[BillyONeal]

Thank you for your suggestion. I checked on https://repology.org/ and did not find any existing project named "high-jump".

That is exactly the problem. By default we don't put 'pretty names' on things because we can always add the pretty name later, but once the pretty name is 'assigned' we can never change it ever again.

Note that this isn't about the name of your library. The vcpkg port named hanjingo-high-jump can install a library named just high-jump.

[hanjingo]

Thank you for your suggestion. I checked on https://repology.org/ and did not find any existing project named "high-jump".

That is exactly the problem. By default we don't put 'pretty names' on things because we can always add the pretty name later, but once the pretty name is 'assigned' we can never change it ever again.

Note that this isn't about the name of your library. The vcpkg port named hanjingo-high-jump can install a library named just high-jump.

Repo renamed to hanjingo/hanjingo-high-jump and portfile updated