[Vmaware] add new port

[t43rr7]

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

[t43rr7]

There's a note about 'usage' file. This library is header only and doesn't contain any 'usage' which can be easily generated. What should I do to add proper usage?

[MichalPetryka]

Should the GPL header maybe be under a separate feature to avoid accidental usage?

[t43rr7]

Do you propose to install headers with the same name but kinda 'toggle' which one should be installed depends on "gpl" feature enabled? If so, I think it's a good idea.

[JonLiu1993]

@t43rr7, Thanks for your new port. Could you please change the name of the port? It is difficult to find your repository kernelwernel/VMAware when searching for this port name, because it will pop up a lot of "VMware" official content, which will confuse users.

[t43rr7]

What name do you suggest?

[JonLiu1993]

What about kernelwernel-VMAware?

[JonLiu1993]

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

[dg0yt]

A gpl feature also exist in ffmpeg.
FTR the suggested implementation here is not fool-proof: When one dependency activates gpl3, all other packages will get the GPL-licensed header, too.

[dg0yt]

Suggested change

	"license": "GPL-3.0-only OR MIT",
	"features": {
	"gpl3": {
	"description": "Enable GPL-3.0 compatible code"
	"license": "MIT",
	"features": {
	"gpl3": {
	"description": "Enable GPL-3.0 licensed code",
	"license": "GPL-3.0-only"