[wolf-midi] Add new port

[wolfgitpr]

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

[JonLiu1993]

Thanks for your new port. Could you please change the name of the port? We have difficulty finding your repository using "cpp-midi c++" and "wolfgitpr/cpp-midi" when searching for this port name because it brings up a lot of other library content, which can be confusing for users. I suggest changing the name to wolfgitpr-midi.

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

[wolfgitpr]

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.

Thank you for your suggestion. The port and repositories have been renamed to "wolf-midi" and can be found.

[JonLiu1993]

Tested usage successfully by wolf-midi:x64-windows:

wolf-midi provides CMake targets:

  find_package(wolf-midi CONFIG REQUIRED)
  target_link_libraries(main PRIVATE wolf-midi::wolf-midi)

[BillyONeal]

:( I'm sorry to do this to you. I observe that both of these appear to be C++ libraries that might be confused:

• https://github.com/wolfgitpr/wolf-midi/
• https://github.com/ericvids/wolfmidi/

If I search the first one is the first hit, and the second one is the second hit. However,
wolf-midi is very close to our 'autoapprove gitorg-repo' form, so I'm going to confirm with other maintainers before asking you to change anything.

If we accept this, then the other one would have to become ericvids-wolfmidi. On the other hand, that one looks like it might be an 'application' and thus not something we would normally index in the first place...

/cc @ericvids

[BillyONeal]

Packaging in progress....

[ericvids]

:( I'm sorry to do this to you. I observe that both of these appear to be C++ libraries that might be confused:

• https://github.com/wolfgitpr/wolf-midi/
• https://github.com/ericvids/wolfmidi/

If I search the first one is the first hit, and the second one is the second hit. However, wolf-midi is very close to our 'autoapprove gitorg-repo' form, so I'm going to confirm with other maintainers before asking you to change anything.

If we accept this, then the other one would have to become ericvids-wolfmidi. On the other hand, that one looks like it might be an 'application' and thus not something we would normally index in the first place...

/cc @ericvids

@BillyONeal, I do not agree with your request for the following reasons:

1. My wolfmidi project is NOT a C++ library, it is a mod for the game Wolfenstein 3-D and is irrelevant to your project.
2. "Searching the first one is the first hit" is a contentious reason to change another project's name. My project has been active since 2021 and is already referenced in build automation scripts in other game-preservation community projects outside of github. The wolf-midi repository is only created this month. Conversely, if you do a Google or Bing search for "wolfmidi", it's my project that comes up, and not wolf-midi.

[BillyONeal]

"Searching the first one is the first hit" is a contentious reason to change another project's name.

@ericvids The reason we do that is we want someone who does "vcpkg install Xxx" to not be "surprised" in getting a different thing than they thought they were installing. The first priority here is repology, and if we get no hits, plain search engines are the backup. If we can't resolve potential confusion, we default to requiring exactly org-repo, which here would be wolfgitpr-wolf-midi.

The rationale is that hopefully the first hit surprises the fewest people. Once we index something under a name, we can't really change what that name means because that would break people.

There's no ask to rename someone's project, only an acknowledgement that vcpkg install thing can only have one meaning.

My wolfmidi project is NOT a C++ library, it is a mod for the game Wolfenstein 3-D and is irrelevant to your project.

Then we need not be concerned about such confusion. Thanks for confirming!

[BillyONeal]

@ericvids @wolfgitpr Sorry for the confusion, upon confirming the name @JavierMatosD @vicroms @ras0219-msft and I realize that the above discussion could have been interpreted as saying that the name of the project itself needs to change. We are only concerned here with what the name of the port in vcpkg is, please call your project whatever you want :)

None of us have a problem with wolf-midi here. @wolfgitpr Given the confusion above, did you want to change the name of your project back to something else or are you happy with how this is?

[wolfgitpr]

@ericvids @wolfgitpr Sorry for the confusion, upon confirming the name @JavierMatosD @vicroms @ras0219-msft and I realize that the above discussion could have been interpreted as saying that the name of the project itself needs to change. We are only concerned here with what the name of the port in vcpkg is, please call your project whatever you want :)

None of us have a problem with wolf-midi here. @wolfgitpr Given the confusion above, did you want to change the name of your project back to something else or are you happy with how this is?

The original name 'cpp-midi' is indeed difficult to search for, and I have no objection to the current 'wolf-midi'. Thank you for your review comments.

[BillyONeal]

Thanks for the new port and sorry for any confusion!