add ultrack

[JoOkuma]

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 (ultrack) and found some lint.

Here's what I've got...

For ultrack:

• The home item is expected in the about section.
• The summary item is expected in the about section.
• Please do not delete the example recipe found in recipes/example/meta.yaml.
• The following maintainers have not yet confirmed that they are willing to be listed here: ilan-theodoro. Please ask them to comment on this PR if they are.

[JoOkuma]

@ilan-theodoro, do you agree to be a maintainer of this conda recipe?

[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 (ultrack) and found some lint.

Here's what I've got...

For ultrack:

• Please do not delete the example recipe found in recipes/example/meta.yaml.
• The following maintainers have not yet confirmed that they are willing to be listed here: ilan-theodoro. Please ask them to comment on this PR if they are.

[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/ultrack) and found some lint.

Here's what I've got...

For recipes/ultrack:

• The top level meta key channel_targets is unexpected
• The following maintainers have not yet confirmed that they are willing to be listed here: ilan-theodoro. Please ask them to comment on this PR if they are.

[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/ultrack) and found some lint.

Here's what I've got...

For recipes/ultrack:

• The following maintainers have not yet confirmed that they are willing to be listed here: ilan-theodoro. Please ask them to comment on this PR if they are.

[ilan-theodoro]

🔥

[synapticarbors]

Please do not modify these files under .ci_support. You should only be adding files under the recipe directory that you are building the package for. Additionally any dependencies need to be pulled in from the conda-forge channel. If it's not available, then that package needs to be added to conda-forge.

[JoOkuma]

@synapticarbors thank you for the feedback.

gurobi is a closed-source package from a private company. I think it's very unlikely they will include it in conda-forge since they have their own gurobi channel.

Does that mean I won't be able to add my package to conda-forge? If so, do you have any suggestions for uploading it to conda? Maybe I should create my own channel?