I am following the conda tutorial for using conda-build here which says to create a meta.yaml file so conda-build can create the conda package. This tutorial uses click as an example, and I know click has a conda package in my conda channel mirror, so I know it somehow has a way to be built by conda. However the github does not contain a meta.yaml file, but instead a uv and pyproject.toml file. In fact, I cant find a meta.yaml file in other big projects such as pandas or numpy. and meta.yaml seems to be doing the same thing as pyproject.toml but it is incompatible with it. So I am confused on where meta.yaml should fit into my build pipeline.
I see conda-forge seems to have an automated workflow for creating the build templates and the build information is stored entirely separated from the source code of the underlying package. I'm not sure why this cant be included with the source code.
If I am storing packages in a custom local conda channel, should I be following this and keeping a github project with all the builds or can I just store meta.yaml in the root of my project in lieu of pyproject.toml if I only want to have a conda build of the package and dont care about directly installing using pip?
