Adding a TAK server and its support packages

[phreed]

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.

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

• pixi.toml:
  • lints:
    • Do not edit files outside of the recipes/ directory.

[conda-forge-admin]

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/testresources/recipe.yaml, recipes/digitalpy/recipe.yaml, recipes/asyncio/recipe.yaml, recipes/freetakserver/recipe.yaml) and found it was in an excellent condition.

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

For recipes/testresources/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

For recipes/digitalpy/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

For recipes/asyncio/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

For recipes/freetakserver/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the test.requires section of recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13529475900. Examine the logs at this URL for more detail.}

[phreed]

I have questions regarding the dependency packages.
Should I split them out into separate feedstocks?
DigitalPy is from the same group as FreeTAKServer but testresources and asyncio are from different sources.

I read https://conda-forge.org/docs/maintainer/adding_pkgs/#packaging-the-license-manually
but I am unclear, should I use the conda-forge license produced by grayskull or use the same license as used by the source? And if from the source should I copy it or just provide a link into the source?

[phreed]

The example-v1/README.md has some defects:

# V1 recipe format

This recipe is an example of the v1 recipe format.
* [CEP 13](https://github.com/conda/ceps/blob/main/cep-0013.md)
* [CEP 14](https://github.com/conda/ceps/blob/main/cep-0014.md)

The v1 recipe format is fully functional when built with rattler-build,
but is not yet fully supported by conda-forge's automation.

See https://github.com/conda-forge/conda-forge.github.io/issues/2308 for progress on general support for this new format.

[phreed]

@conda-forge/help-python

[phreed]

I would like to modify the pixi.toml file to work with the v1 format.

[feature.grayskull.dependencies]
grayskull = ">=2.7.3"
conda-recipe-manager = ">=0.4.1"
[feature.grayskull.tasks.pypi]
description = "generate a recipe for a PyPI package name with `grayskull`"
cmd = "cd recipes && grayskull pypi --strict-conda-forge --use-v1-format"

Maybe add it in as a new task.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[phreed]

I see that the win_64 build is failing. How can I get more information on the issue?