Adding the USNISTGOV SCTK (word error rate scoring toolkit) as a conda package

[egaznep]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found some lint.

Here's what I've got...

For recipes/sctk:

• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.

For recipes/sctk:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[github-actions]

Hi! Thanks for your contribution to conda-forge.
When submitting a pull request, please do not change anything in the example recipe.
Please make sure that any changes are reverted before you submit it for review.
Thanks!

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found some lint.

Here's what I've got...

For recipes/sctk:

• The summary item is expected in the about section.
• The recipe must have some tests.
• The recipe must have a build/number section.
• Please do not delete the example recipe found in recipes/example/meta.yaml.

For recipes/sctk:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found some lint.

Here's what I've got...

For recipes/sctk:

• The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'requirements', 'about', 'extra'].
• The summary item is expected in the about section.
• The recipe must have some tests.

For recipes/sctk:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[egaznep]

@conda-forge-admin, please ping team @conda-forge/help-c-cpp

I need help regarding the license file. Even though SPDX lists NIST-Software as a valid identifier, the linter complains about it.
(I plan to resolve rest of the issues myself)

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/staged-recipes and so here I am doing that.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found it was in an excellent condition.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found some lint.

Here's what I've got...

For recipes/sctk:

• Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found some lint.

Here's what I've got...

For recipes/sctk:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [13, 21, 25]

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found it was in an excellent condition.

[carterbox]

Suggested change

	license: LicenseRef-NIST-Software
	license: NIST-Software

This license is not yet added to our linting tool. Probably because the list of allowed licenses hasn't been updated in a year. Please open a PR like this one on the conda-smithy feedstock with the updated licenses. (Note that there is a tool provided to autogenerate the list).

[carterbox]

If you want to run make check, please do it as part of the build script instead of including a copy of the entire source tree in the package.

My understanding is that this package is a collection of CLI tools, so the tests section should be calling "$ tool --help" or like "$ tool --version", to check that they return without error.

[egaznep]

I understand. Unfortunately the developer did not add either option. What would be the recommendation in this case, simply checking for the existence of the files?

[carterbox]

Suggested change

- cmake

There appears to be no CMakeLists.txt in the upstream project, so CMake is probably not needed.

[egaznep]

I did this change myself, should've "accepted your suggestion" instead. I would be glad if you could re-check.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/espeak-ng, recipes/pcaudiolib, recipes/sctk) and found some lint.

Here's what I've got...

For recipes/pcaudiolib:

• The recipe must have some tests.

For recipes/pcaudiolib:

• Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [9].

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/sctk) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/sctk:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[egaznep]

@conda-forge-admin, please ping team @conda-forge/help-c-cpp, ready for review!

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/staged-recipes and so here I am doing that.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, or conda-forge/help-ruby. Thanks!