Add dooit-extras

[claudiushaag]

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 your PR looks excellent! 🚀

[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/dooit-extras/recipe.yaml) and found it was in an excellent condition.

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

For recipes/dooit-extras/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use python >=${{ python_min }} for the python entry.
  • For the test.requires section of the 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/12253333655. Examine the logs at this URL for more detail.}

[claudiushaag]

@conda-forge/help-python , ready for review!

[conda-forge-admin]

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/dooit-extras/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/dooit-extras/recipe.yaml:

• ❌ noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

For recipes/dooit-extras/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use python >=${{ python_min }} for the python entry.
  • For the test.requires section of the 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/12253732844. Examine the logs at this URL for more detail.}

[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/dooit-extras/recipe.yaml) and found it was in an excellent condition.

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

For recipes/dooit-extras/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the test.requires section of the 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/12434918155. Examine the logs at this URL for more detail.}

[claudiushaag]

@ocefpaf, I changed the recipe as you suggested, but it seems as rattler-build does not have access to python_min. Could this be related to #2351 or #28445, where problems with python_min are also present?

I would now tend to keep the context and keep my eye on how this problem is tackled.

[ocefpaf]

@wolfv what is the recommendation here for the new recipe format?