[eljonny-testcpp]: new port

[eljonny]

I would like to add my library TestCPP to the public vcpkg registry.
It is a very simple C++ testing framework that can be useful for small or educational projects.

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

[eljonny]

@microsoft-github-policy-service agree

[eljonny]

I am concerned that since my package does not exist on repology.org.
Since it is quite new to GitHub and the internet (I hadn't published the source to a public repository previous to creating the repo in my GitHub) it is not yet easily found on search engines.
So I really can't check the 2nd box off on the checklist. Is that going to block my PR from being approved?

TestCPP is a personal project I wrote many years ago that I am coming back to, as I am looking to improve it and add it to current C++ package registries, which I had not done previously.
There appears to be a similarly named test framework on GitHub called test-cpp, but it appears to be abandoned as it has not been updated for about 10 years. Would this be considered a naming conflict? If so I can rename my package since this is the first time I'm actually publishing it.

Thanks so much for looking at my request.
Jonathan

[BillyONeal]

Web search for this name first hit is https://github.com/mrts/test-cpp

Would you accept eljonny-testcpp?

[BillyONeal]

Also, Test.h and tests.hpp are likely to conflict with other users. Can you install those to a subdirectory?

[eljonny]

I'll work out a different name for the package.
The test.hpp file is totally local to the project and is used for the demo application that users can build when learning the library. Test.h goes into a subdirectory called TestCPP when installed; so it will go to /install/prefix/include/TestCPP/Test.h.
Is this ok?
I appreciate you checking out my PR! Thank you!

[eljonny]

Would the name basictestcpp be ok?
It looks like that one comes back pretty empty on search.
If this is ok I'll fix that up, if not I'll use eljonny-testcpp.
Thanks again!

[BillyONeal]

Test.h goes into a subdirectory called TestCPP when installed; so it will go to /install/prefix/include/TestCPP/Test.h.

This is fine if we keep the name TestCPP. If so your documentation should tell people to do #include <TestCPP/Test.h>

Would the name basictestcpp be ok?
It looks like that one comes back pretty empty on search.
If this is ok I'll fix that up, if not I'll use eljonny-testcpp.

To be clear, the check is not 'is that name unused', it is 'is that name strongly associated with that already'. With the overall goal being that someone doing vcpkg install name getting what they expect name to mean.

[BillyONeal]

I'll ask other maintainers but eljonny-testcpp would be ideal as following GitHub's names are ~always acceptable.

[eljonny]

Test.h goes into a subdirectory called TestCPP when installed; so it will go to /install/prefix/include/TestCPP/Test.h.

This is fine if we keep the name TestCPP. If so your documentation should tell people to do #include <TestCPP/Test.h>

This information is indeed currently in the docs (README.md in the repo).
I don't have any intention of changing the actual library name.
If I were to change the package name, would adding the package to vcpkg require me to rename the actual library?

Would the name basictestcpp be ok?

It looks like that one comes back pretty empty on search.

If this is ok I'll fix that up, if not I'll use eljonny-testcpp.

To be clear, the check is not 'is that name unused', it is 'is that name strongly associated with that already'. With the overall goal being that someone doing vcpkg install name getting what they expect name to mean.

Ahhh ok I understand. This makes sense. I'm more than happy changing the package name to eljonny-testcpp.

[eljonny]

I'll ask other maintainers but eljonny-testcpp would be ideal as following GitHub's names are ~always acceptable.

I will rename the package to eljonny-testcpp. This is no biggie. Thank you for all your input and info!

[BillyONeal]

Sorry, I think this fell through the cracks because:

1. It was still marked draft
2. The name change you said you would do in [eljonny-testcpp]: new port #37471 (comment) had not actually happened yet

Because we've kept you in a holding pattern for so long I applied those changes for you and fixed the usage to be brief enough to be OK (we got a lot of feedback that people didn't like a book of usage text).

I think this is OK now but I need another maintainer to OK it.

[eljonny]

@BillyONeal And @vicroms thank you both so much!